| Finding ID |
Severity |
Title |
Description |
|
V-223856
|
High |
IBM z/OS UID(0) must be properly assigned. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223838
|
High |
The IBM z/OS UNIX SUPERUSER resources must be protected in accordance with guidelines. |
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... |
|
V-223837
|
High |
IBM RACF LOGONIDs must not be defined to SYS1.UADS for non-emergency use. |
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. |
|
V-223810
|
High |
IBM z/OS SSH daemon must be configured to only use the SSHv2 protocol. |
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.
Operating systems are capable of providing a wide variety of functions and... |
|
V-223807
|
High |
The IBM RACF SSH daemon must be configured to use a FIPS 140-2 compliant cryptographic algorithm to protect confidential information and remote access sessions. |
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. Cryptographic modules must adhere to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
Remote access (e.g., RDP) is access to DoD nonpublic information systems... |
|
V-223788
|
High |
The IBM z/OS systems requiring data-at-rest protection must properly employ IBM DS8880 or equivalent hardware solutions for full disk encryption. |
This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. Operating systems handling data requiring "data at rest" protections must... |
|
V-223781
|
High |
Unsupported system software must not be installed and/ or active on the system. |
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.
Some of the... |
|
V-223777
|
High |
IBM RACF must define UACC of NONE on all profiles. |
The operating system must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs. |
|
V-223760
|
High |
IBM RACF must be installed and active on the system. |
Enterprise environments make account management for operating systems challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other errors. IBM z/OS requires an external security manager to assure proper account management. |
|
V-223729
|
High |
NIST FIPS-validated cryptography must be used to protect passwords in the security database. |
Password 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.
Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for... |
|
V-223704
|
High |
The IBM RACF PROTECTALL SETROPTS value specified must be properly set. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223703
|
High |
IBM RACF must define WARN = NO on all profiles. |
Failure to restrict system access to authenticated users negatively impacts operating system security. |
|
V-223697
|
High |
IBM z/OS SYS1.PARMLIB must be properly protected. |
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate,... |
|
V-223687
|
High |
IBM RACF must limit all system PROCLIB data sets to system programmers only. |
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... |
|
V-223685
|
High |
IBM RACF security data sets and/or databases must be properly protected. |
The External Security Manager (ESM) database files contain all access control information for the operating system environment and system resources. Unauthorized access could result in the compromise of the operating system environment, ACP, and customer data.
Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000134-GPOS-00068, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125 |
|
V-223684
|
High |
The IBM RACF System REXX IRRPWREX security data set must be properly protected. |
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... |
|
V-223682
|
High |
IBM RACF must limit WRITE or greater access to all APF-authorized libraries to system programmers only. |
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... |
|
V-223679
|
High |
IBM RACF must limit Write or greater access to libraries containing EXIT modules to system programmers only. |
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... |
|
V-223678
|
High |
IBM RACF must limit write or greater access to all LPA libraries to system programmers only. |
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... |
|
V-223677
|
High |
IBM z/OS libraries included in the system REXXLIB concatenation must be properly protected. |
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,... |
|
V-223676
|
High |
IBM RACF must limit Write or greater access to SYS1.LPALIB to system programmers only. |
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... |
|
V-223675
|
High |
IBM RACF must limit Write or greater access to SYS1.SVCLIB to appropriate authorized users. |
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... |
|
V-223674
|
High |
IBM RACF must limit Write or greater access to SYS1.IMAGELIB to system programmers only. |
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... |
|
V-223668
|
High |
IBM z/OS must protect dynamic lists in accordance with proper security requirements. |
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... |
|
V-223667
|
High |
IBM RACF must limit Write or greater access to SYS1.UADS to system programmers only, and WRITE or greater access must be limited to system programmer personnel and/or security personnel. |
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... |
|
V-223666
|
High |
IBM RACF access to the System Master Catalog must be properly protected. |
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... |
|
V-223649
|
High |
IBM RACF must limit Write or greater access to SYS1.NUCLEUS to system programmers only. |
This data set contains a large portion of the system initialization (IPL) programs and pointers to the master and alternate master catalog. Unauthorized access could result in the compromise of the operating system environment, ACP, and customer data.
Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125 |
|
V-257135
|
Medium |
IBM Passtickets must be configured to be KeyEncrypted. |
Passwords such as IBM Passtickets need to be protected at all times, and encryption is the standard method for protecting such passwords. If passwords are not encrypted, they may be plainly read (i.e., clear text) and easily compromised. |
|
V-255939
|
Medium |
IBM Integrated Crypto Service Facility (ICSF) STC data sets must be properly protected. |
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... |
|
V-255938
|
Medium |
IBM Integrated Crypto Service Facility (ICSF) Started task(s) must be properly defined to the STARTED resource class for RACF. |
Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data. |
|
V-255937
|
Medium |
IBM Integrated Crypto Service Facility (ICSF) Started Task name is not properly identified / defined to the system ACP. |
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... |
|
V-255936
|
Medium |
IBM Integrated Crypto Service Facility (ICSF) install data sets are not properly protected. |
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. |
|
V-255935
|
Medium |
IBM Integrated Crypto Service Facility (ICSF) Configuration parameters must be correctly specified. |
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. |
|
V-252553
|
Medium |
IBM z/OS TCP/IP AT-TLS policy must be properly configured in Policy Agent. |
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.
This requirement addresses auditing-related issues associated with maintenance tools used specifically for diagnostic and repair actions on organizational information systems.
Nonlocal maintenance and diagnostic activities... |
|
V-251107
|
Medium |
IBM z/OS sensitive and critical system data sets must not exist on shared DASDs. |
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.,... |
|
V-245536
|
Medium |
The IBM z/OS TCPIP.DATA configuration statement must contain the DOMAINORIGIN or DOMAIN specified for each TCP/IP defined. |
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... |
|
V-235033
|
Medium |
IBM RACF must limit WRITE or greater access to LINKLIST libraries to system programmers only. |
The primary function of the LINKLIST is to serve as a single repository for commonly used system modules. Failure to ensure that the proper set of libraries is designated for LINKLIST can impact system integrity, performance, and functionality. For this reason, controls must be employed to ensure that the correct... |
|
V-230210
|
Medium |
IBM RACF exit ICHPWX11 for password phrases must be installed and properly configured. |
Use of a complex password phrase helps to increase the time and resources required to compromise the password. Password phrase complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password phrase complexity is one factor of several that determines... |
|
V-230209
|
Medium |
The IBM RACF System REXX IRRPHREX security data set must be properly protected. |
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... |
|
V-223870
|
Medium |
IBM z/OS VTAM USSTAB definitions must not be used for unsecured terminals. |
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. |
|
V-223869
|
Medium |
IBM z/OS System datasets used to support the VTAM network must be properly secured. |
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... |
|
V-223868
|
Medium |
The IBM z/OS UNIX Telnet server warning banner must be properly specified. |
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. |
|
V-223867
|
Medium |
IBM z/OS UNIX Telnet server Startup parameters must be properly specified. |
The z/OS UNIX Telnet Server (i.e., otelnetd) provides interactive access to the z/OS UNIX shell. During the initialization process, startup parameters are read to define the characteristics of each otelnetd instance. Some of these parameters have an impact on system security. Failure to specify the appropriate command options could result... |
|
V-223866
|
Medium |
The IBM z/OS UNIX Telnet Server etc/banner file must have the Standard Mandatory DoD Notice and Consent Banner. |
A logon banner can be used to inform users about the environment during the initial logon. 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... |
|
V-223865
|
Medium |
IBM z/OS HFS objects for the z/OS UNIX Telnet Server must be properly protected. |
HFS directories and files of the z/OS UNIX Telnet Server provide the configuration and executable properties of this product. Failure to properly secure these objects may lead to unauthorized access resulting in the compromise of the integrity and availability of the operating system environment, ACP, and customer data.
Satisfies: SRG-OS-000080-GPOS-00048,... |
|
V-223864
|
Medium |
The IBM z/OS startup user account for the z/OS UNIX Telnet Server must be properly defined. |
The PROFILE.TCPIP configuration file provides system operation and configuration parameters for the TN3270 Telnet Server. Several of these parameters have potential impact to system security. Failure to code the appropriate values could result in unexpected operations and degraded security. This exposure may result in unauthorized access impacting data integrity or... |
|
V-223863
|
Medium |
IBM z/OS attributes of UNIX user accounts used for account modeling must be defined in accordance with security requirements. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223862
|
Medium |
IBM z/OS UNIX user accounts must be properly defined. |
To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223861
|
Medium |
The IBM z/OS user account for the UNIX (RMFGAT) must be properly defined. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223860
|
Medium |
The IBM z/OS user account for the z/OS UNIX SUPERUSER userid must be properly defined. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223859
|
Medium |
The IBM z/OS user account for the UNIX kernel (OMVS) must be properly defined to the security database. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. |
|
V-223857
|
Medium |
IBM z/OS UNIX groups must be defined with a unique GID. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. RACF userid groups, and started tasks that use z/OS UNIX facilities are defined to an ACP with attributes including UID and GID. If these attributes are not... |
|
V-223855
|
Medium |
IBM z/OS UNIX security parameters for restricted network service(s) in /etc/inetd.conf must be properly specified. |
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.
Operating systems are capable of providing a wide variety of functions and... |
|
V-223854
|
Medium |
IBM z/OS UNIX HFS MapName files security parameters must be properly specified. |
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.
The organization must perform a periodic scan/review of the application (as required by CCI-000384) and disable functions, ports, protocols, and services deemed... |
|
V-223853
|
Medium |
IBM z/OS default profiles must be defined in the corresponding FACILITY Class Profile for classified systems. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223852
|
Medium |
IBM z/OS UNIX BPXPRMxx security parameters in PARMLIB must be properly specified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223851
|
Medium |
IBM z/OS UNIX OMVS parameters in PARMLIB must be properly specified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223850
|
Medium |
The IBM RACF classes required to properly secure the z/OS UNIX environment must be ACTIVE. |
In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations. |
|
V-223849
|
Medium |
IBM z/OS UNIX MVS data sets used as step libraries in /etc/steplib must be properly protected. |
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... |
|
V-223848
|
Medium |
IBM z/OS UNIX SYSTEM FILE SECURITY SETTINGS must be properly protected or specified. |
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.
Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100 |
|
V-223847
|
Medium |
IBM z/OS UNIX HFS permission bits and audit bits for each directory must be properly protected. |
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... |
|
V-223846
|
Medium |
IBM z/OS UNIX MVS data sets WITH z/OS UNIX COMPONENTS must be properly protected. |
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... |
|
V-223845
|
Medium |
IBM z/OS UNIX MVS data sets or HFS objects must be properly protected. |
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... |
|
V-223844
|
Medium |
IBM z/OS UNIX resources must be protected in accordance with security requirements. |
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... |
|
V-223843
|
Medium |
IBM z/OS UNIX security parameters in /etc/rc must be properly specified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223842
|
Medium |
IBM z/OS UNIX security parameters in etc/profile must be properly specified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223840
|
Medium |
IBM z/OS UNIX MVS HFS directories with other write permission bit set must be properly defined. |
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... |
|
V-223839
|
Medium |
IBM z/OS BPX resource(s) must be protected in accordance with security requirements. |
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... |
|
V-223836
|
Medium |
IBM Z/OS TSOAUTH resources must be restricted to authorized users. |
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... |
|
V-223835
|
Medium |
The IBM z/OS PROFILE.TCPIP configuration for the TN3270 Telnet server must have the INACTIVE statement properly specified. |
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... |
|
V-223834
|
Medium |
IBM z/OS VTAM session setup controls for the TN3270 Telnet server must be properly specified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223833
|
Medium |
The IBM z/OS warning banner for the TN3270 Telnet server must contain the proper content of the Standard Mandatory DoD Notice and Consent Banner. |
System use notifications are required only for access via logon interfaces with human users and are not required when such human interfaces do not exist. |
|
V-223831
|
Medium |
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. |
During the SSL connection process a mutually acceptable encryption algorithm is selected by the server and client. This algorithm is used to encrypt the data that subsequently flows between the two. However, the level or strength of encryption can vary greatly. Certain configuration options can allow no encryption to be... |
|
V-223827
|
Medium |
IBM z/OS Configuration files for the TCP/IP stack must be properly specified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223826
|
Medium |
IBM z/OS data sets for the Base TCP/IP component must be properly protected. |
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.... |
|
V-223824
|
Medium |
The IBM RACF SERVAUTH resource class must be active for TCP/IP resources. |
IBM Provides the SERVAUTH Class for use in protecting a variety of TCP/IP features/functions/products both IBM and third-party. Failure to activate this class will result in unprotected resources. This exposure may threaten the integrity of the operating system environment, and compromise the confidentiality of customer data. |
|
V-223823
|
Medium |
IBM z/OS TCP/IP resources must be properly protected. |
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... |
|
V-223822
|
Medium |
IBM z/OS permission bits and user audit bits for HFS objects that are part of the Base TCP/IP component must be properly configured. |
HFS directories and files of the Base TCP/IP component provide the configuration, operational, and executable properties of IBMs TCP/IP system product. Failure to properly secure these objects may lead to unauthorized access resulting in the compromise of the integrity and availability of the operating system environment, ACP, and customer data. |
|
V-223821
|
Medium |
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. |
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.
Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through... |
|
V-223820
|
Medium |
IBM z/OS PROFILE.TCPIP configuration statements for the TCP/IP stack must be coded properly. |
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.
Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through... |
|
V-223819
|
Medium |
IBM z/OS using DFSMS must properly specify SYS(x).PARMLIB(IGDSMSxx), SMS parameter settings. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223818
|
Medium |
IBM z/OS DFSMS resources must be protected in accordance with the proper security requirements. |
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... |
|
V-223817
|
Medium |
IBM z/OS DFSMS-related RACF classes must be active. |
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... |
|
V-223816
|
Medium |
IBM z/OS DFSMS control data sets must be protected in accordance with security requirements. |
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... |
|
V-223815
|
Medium |
IBM z/OS DFSMS Program Resources must be properly defined and protected. |
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... |
|
V-223814
|
Medium |
The IBM z/OS Syslog daemon must be properly defined and secured. |
The Syslog daemon, known as syslogd, is a zOS UNIX daemon that provides a central processing point for log messages issued by other zOS 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... |
|
V-223813
|
Medium |
The IBM z/OS Syslog daemon must be started at z/OS initialization. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223812
|
Medium |
IBM z/OS permission bits and user audit bits for HFS objects that are part of the Syslog daemon component must be properly configured. |
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. |
|
V-223811
|
Medium |
IBM z/OS, for PKI-based authentication, must use the ICSF or ESM for key management. |
Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis. |
|
V-223809
|
Medium |
The SSH daemon must be configured with the Standard Mandatory DoD Notice and Consent Banner. |
|
|
V-223806
|
Medium |
IBM z/OS SMF recording options for the SSH daemon must be configured to write SMF records for all eligible events. |
SMF data collection is the basic unit of tracking of all system functions and actions. Included in this tracking data are the audit trails from each of the ACPs. If the control options for the recording of this tracking are not properly maintained, then accountability cannot be monitored, and its... |
|
V-223805
|
Medium |
IBM z/OS system administrator must develop a procedure to offload SMF files to a different system or media than the system being audited. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity. |
|
V-223804
|
Medium |
IBM z/OS must 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. |
If anomalies are not acted upon, security functions may fail to secure the system.
Security 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... |
|
V-223803
|
Medium |
IBM z/OS system administrator must develop a procedure to remove all software components after updated versions have been installed. |
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. |
|
V-223801
|
Medium |
IBM z/OS system administrator must develop a procedure to provide an audit reduction capability that supports on-demand reporting requirements. |
The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents.
Audit reduction is a process that manipulates collected audit information and organizes such... |
|
V-223800
|
Medium |
IBM z/OS system administrator must develop a procedure to notify designated personnel if baseline configurations are changed in an unauthorized manner. |
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.
Detecting such changes and providing an automated response can help... |
|
V-223798
|
Medium |
IBM z/OS system administrator must develop a procedure to remove or disable temporary user accounts after 72 hours. |
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... |
|
V-223797
|
Medium |
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. |
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.
The session lock is implemented at the point where session... |
|
V-223796
|
Medium |
IBM z/OS must employ a session for users to directly initiate a session lock for all connection types. |
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.
The session lock is implemented at the point where session... |
|
V-223795
|
Medium |
IBM z/OS must employ a session manager to manage session lock after a 15-minute period of inactivity. |
A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their operating... |
|
V-223794
|
Medium |
The IBM z/OS must employ a session manager that conceals, via the session lock, information previously visible on the display with a publicly viewable image. |
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.
The session lock is implemented at the point where session activity can... |
|
V-223793
|
Medium |
The IBM z/OS Policy Agent must contain a policy that manages excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial-of-service (DoS) attacks. |
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. |
|
V-223792
|
Medium |
The IBM z/OS Policy Agent must contain a policy that protects against or limits the effects of denial-of-service (DoS) attacks by ensuring the operating system is implementing rate-limiting measures on impacted network interfaces. |
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. |
|
V-223786
|
Medium |
IBM z/OS LNKAUTH=APFTAB must be specified in the IEASYSxx member(s) in the currently active parmlib data set(s). |
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. |
|
V-223785
|
Medium |
IBM zOS inapplicable PPT entries must be invalidated. |
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.
Operating systems are capable of providing a... |
|
V-223784
|
Medium |
IBM z/OS must not have inaccessible APF libraries defined. |
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.
Operating systems are capable of providing a... |
|
V-223783
|
Medium |
IBM z/OS must not allow nonexistent or inaccessible Link Pack Area (LPA) libraries. |
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.
Some of the... |
|
V-223782
|
Medium |
IBM z/OS must not allow nonexistent or inaccessible LINKLIST libraries. |
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.
Some of the... |
|
V-223780
|
Medium |
The IBM z/OS Policy Agent must employ a deny-all, allow-by-exception firewall policy for allowing connections to other systems. |
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. |
|
V-223778
|
Medium |
IBM z/OS PASSWORD data set and OS passwords must not be used. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223776
|
Medium |
IBM z/OS PARMLIB CLOCKxx must have the Accuracy PARM properly coded. |
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.
Synchronizing internal information system clocks provides uniformity of time stamps for information... |
|
V-223775
|
Medium |
IBM z/OS SNTP daemon (SNTPD) permission bits must be properly configured. |
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.
Synchronizing internal... |
|
V-223774
|
Medium |
The IBM z/OS SNTP daemon (SNTPD) must be active. |
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.
Synchronizing internal... |
|
V-223773
|
Medium |
IBM z/OS NOBUFFS in SMFPRMxx must be properly set (default is MSG). |
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... |
|
V-223772
|
Medium |
IBM z/OS BUFUSEWARN in the SMFPRMxx must be properly set. |
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.
Audit processing... |
|
V-223771
|
Medium |
IBM z/OS system administrators must develop an automated process to collect and retain SMF data. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information systems with limited audit storage capacity. |
|
V-223770
|
Medium |
IBM z/OS SMF collection files (system MANx datasets or LOGSTREAM DASD) must have storage capacity to store at least one weeks worth of audit data. |
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.
The task of allocating audit record storage capacity is usually performed during initial installation of the operating system. |
|
V-223769
|
Medium |
IBM z/OS must specify SMF data options to assure appropriate activation. |
SMF data collection is the basic unit of tracking of all system functions and actions. Included in this tracking data are the audit trails from each of the ACPs. If the control options for the recording of this tracking are not properly maintained, then accountability cannot be monitored, and its... |
|
V-223768
|
Medium |
IBM z/OS must employ a session manager to manage display of the Standard Mandatory DoD Notice and Consent Banner. |
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. All methods of gaining access to the system must comply with this requirement to... |
|
V-223767
|
Medium |
IBM z/OS required SMF data record types must be collected. |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
To address access requirements,... |
|
V-223766
|
Medium |
The IBM z/OS system administrator (SA) must develop a process to notify information system security officers (ISSOs) of account enabling actions. |
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 SAs and ISSOs is one method for... |
|
V-223765
|
Medium |
The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are removed. |
When operating system accounts are removed, 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 removal events to the SAs and information system security officers (ISSOs) is one method for mitigating this risk. Such... |
|
V-223764
|
Medium |
The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are deleted. |
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. |
|
V-223763
|
Medium |
The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are modified. |
Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. |
|
V-223762
|
Medium |
The IBM z/OS system administrator (SA) must develop a process to notify appropriate personnel when accounts are created. |
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... |
|
V-223761
|
Medium |
The IBM z/OS system administrator (SA) must develop a process to disable emergency accounts after the crisis is resolved or 72 hours. |
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... |
|
V-223759
|
Medium |
IBM z/OS SMF recording options for the TN3270 Telnet Server must be properly specified. |
The TN3270 Telnet Server can provide audit data in the form of SMF records. The SMF data produced provides information about individual sessions. This data includes the VTAM application, the remote and local IP addresses, and the remote and local IP port numbers. Failure to collect and retain audit data... |
|
V-223758
|
Medium |
The IBM z/OS BPX.SMF resource must be properly configured. |
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.
Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through... |
|
V-223757
|
Medium |
IBM z/OS must configure system wait times to protect resource availability based on site priorities. |
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... |
|
V-223756
|
Medium |
IBM z/OS RJE workstations and NJE nodes must be controlled in accordance with security requirements. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223755
|
Medium |
IBM z/OS surrogate users must be controlled in accordance with proper security requirements. |
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... |
|
V-223754
|
Medium |
IBM z/OS JES2 system commands must be protected in accordance with security requirements. |
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... |
|
V-223753
|
Medium |
IBM z/OS JES2 spool resources must be controlled in accordance with security requirements. |
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... |
|
V-223752
|
Medium |
IBM z/OS JESTRACE and/or SYSLOG resources must be protected in accordance with security requirements. |
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... |
|
V-223751
|
Medium |
IBM z/OS JESNEWS resources must be protected in accordance with security requirements. |
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... |
|
V-223750
|
Medium |
IBM z/OS JESSPOOL resources must be protected in accordance with security requirements. |
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... |
|
V-223749
|
Medium |
IBM z/OS JES2 output devices must be properly controlled for classified systems. |
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... |
|
V-223748
|
Medium |
IBM z/OS JES2 output devices must be controlled in accordance with the proper security requirements. |
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... |
|
V-223747
|
Medium |
IBM z/OS JES2 input sources must be properly controlled. |
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... |
|
V-223746
|
Medium |
IBM z/OS JES2 input sources must be controlled in accordance with the proper security requirements. |
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... |
|
V-223745
|
Medium |
IBM z/OS RJE workstations and NJE nodes must be defined to the FACILITY resource class. |
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,... |
|
V-223744
|
Medium |
IBM z/OS startup parameters for the FTP server must have the INACTIVE statement properly set. |
To address access requirements, many operating systems can be integrated with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. |
|
V-223743
|
Medium |
IBM FTP.DATA configuration for the FTP server must have the INACTIVE statement properly set. |
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... |
|
V-223742
|
Medium |
The IBM z/OS FTP server daemon must be defined with proper security parameters. |
The FTP Server daemon requires special privileges and access to sensitive resources to provide its system services. Failure to properly define and control the FTP Server daemon could lead to unauthorized access. This exposure may result in the compromise of the integrity and availability of the operating system environment, ACP,... |
|
V-223741
|
Medium |
IBM z/OS user exits for the FTP server must not be used without proper approval and documentation. |
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.
Operating systems are capable of providing a wide variety of functions and... |
|
V-223740
|
Medium |
The IBM z/OS TFTP server program must be properly protected. |
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.
Some of the... |
|
V-223739
|
Medium |
IBM z/OS FTP.DATA configuration statements for the FTP Server must be specified in accordance with requirements. |
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). |
|
V-223737
|
Medium |
IBM z/OS FTP.DATA configuration statements for the FTP server must specify the BANNER statement. |
|
|
V-223736
|
Medium |
IBM z/OS FTP.DATA configuration statements must indicate a BANNER statement with the proper content. |
|
|
V-223735
|
Medium |
IBM z/OS data sets for the FTP server must be properly protected. |
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. |
|
V-223734
|
Medium |
IBM RACF permission bits and user audit bits for HFS objects that are part of the FTP server component must be properly configured. |
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. |
|
V-223733
|
Medium |
IBM z/OS SMF recording options for the FTP Server must be configured to write SMF records for all eligible events. |
The FTP Server can provide audit data in the form of SMF records. The SMF data produced by the FTP Server provides transaction information for both successful and unsuccessful FTP commands. Failure to collect and retain audit data may contribute to the loss of accountability and hamper security audit activities.... |
|
V-223732
|
Medium |
IBM RACF DASD Management USERIDs must be properly controlled. |
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... |
|
V-223731
|
Medium |
The IBM RACF ERASE ALL SETROPTS value must be set to ERASE(ALL) on all systems. |
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.,... |
|
V-223728
|
Medium |
The IBM RACF PASSWORD(HISTORY) SETROPTS value must be set to five or more. |
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. HISTORY specifies the number of previous passwords that RACF saves for each USERID and compares with an intended new password. If there is a match with one of the... |
|
V-223727
|
Medium |
IBM RACF SETROPTS PASSWORD(INTERVAL) must be set to 60 days. |
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. INTERVAL specifies the... |
|
V-223726
|
Medium |
The IBM RACF SETROPTS PASSWORD(MINCHANGE) value must be set to 1. |
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... |
|
V-223725
|
Medium |
IBM RACF exit ICHPWX01 must be installed and properly configured. |
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.
Satisfies: SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000072-GPOS-00040, SRG-OS-000266-GPOS-00101, SRG-OS-000480-GPOS-00225 |
|
V-223724
|
Medium |
IBM RACF PASSWORD(RULEn) SETROPTS value(s) must be properly set. |
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised.
Password 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... |
|
V-223723
|
Medium |
The IBM RACF INACTIVE SETROPTS value must be set to 35 days. |
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.
Operating systems need to track periods of inactivity and... |
|
V-223722
|
Medium |
IBM RACF user accounts must uniquely identify system users. |
To assure individual accountability and prevent unauthorized access, organizational users must be individually identified and authenticated.
A group authenticator is a generic account used by multiple individuals. Use of a group authenticator alone does not uniquely identify individual users. Examples of the group authenticator is the UNIX OS "root" user... |
|
V-223721
|
Medium |
The IBM RACF Automatic Data Set Protection (ADSP) SETROPTS value must be set to NOADSP. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223719
|
Medium |
IBM z/OS Started Tasks must be properly identified and defined to RACF. |
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,... |
|
V-223718
|
Medium |
IBM interactive USERIDs defined to RACF must have the required fields completed. |
Interactive users are considered to be users of CICS, IMS, TSO/E, NetView, or other products that support logging on at a terminal. Improper assignments of attributes in the LOGONID record for interactive users may allow users excessive privileges resulting in unauthorized access. |
|
V-223717
|
Medium |
IBM RACF users must have the required default fields. |
Ensure that Every USERID is uniquely identified to the system. Within the USERID record, the user's name, default group, the owner, and the user's passdate or phrasedate fields are completed. This will uniquely identify each user. If these fields are not completed for each user, user accountability will become lost.
|
|
V-223716
|
Medium |
IBM z/OS must properly protect MCS console userid(s). |
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.
Operating systems are capable of providing a wide variety of functions and... |
|
V-223715
|
Medium |
IBM z/OS must properly configure CONSOLxx members. |
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.
Operating systems are capable of providing a wide variety of functions and... |
|
V-223714
|
Medium |
IBM RACF assignment of the RACF OPERATIONS attribute to individual userids must be fully justified. |
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). |
|
V-223713
|
Medium |
IBM RACF use of the RACF SPECIAL Attribute must be justified. |
The 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. |
|
V-223712
|
Medium |
IBM z/OS Batch job user IDs must be properly defined. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223711
|
Medium |
The IBM RACF database must be backed up on a scheduled basis. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223710
|
Medium |
The IBM RACF database must be on a separate physical volume from its backup and recovery datasets. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223709
|
Medium |
IBM RACF use of the AUDITOR privilege must be justified. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223708
|
Medium |
The IBM RACF WHEN(PROGRAM) SETROPTS value specified must be active. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223707
|
Medium |
The IBM RACF TAPEDSN SETROPTS value specified must be properly set. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223706
|
Medium |
The IBM RACF RETPD SETROPTS value specified must be properly set. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223705
|
Medium |
The IBM RACF GRPLIST SETROPTS value must be set to ACTIVE. |
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.
Configuration settings are the set of parameters that can be changed in hardware,... |
|
V-223702
|
Medium |
IBM RACF SETROPTS RVARYPW values must be properly set. |
Failure to provide logical access restrictions associated with changes to system configuration may have significant effects on the overall security of the system.
When 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... |
|
V-223701
|
Medium |
IBM z/OS must limit access for SMF collection files (i.e., SYS1.MANx) to appropriate users and/or batch jobs that perform SMF dump processing. |
SMF data collection is the system activity journaling facility of the z/OS system. Unauthorized access could result in the compromise of logging and recording of the operating system environment, ESM, and customer data.
Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality.... |
|
V-223700
|
Medium |
The IBM RACF REALDSN SETROPTS value must be specified. |
Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. |
|
V-223699
|
Medium |
The IBM RACF SETROPTS SAUDIT value must be specified. |
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Audit records can be generated from various components within the information system (e.g.,... |
|
V-223695
|
Medium |
The IBM RACF PASSWORD(REVOKE) SETROPTS value must be specified to revoke the userid after three invalid logon attempts. |
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-force attacks, is reduced. Limits are imposed by locking the account. |
|
V-223694
|
Medium |
IBM RACF OPERAUDIT SETROPTS value must set to OPERAUDIT. |
Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and... |
|
V-223693
|
Medium |
The IBM z/OS JES(XBMALLRACF) SETROPTS value must be set to JES(XBMALLRACF). |
In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.... |
|
V-223692
|
Medium |
The IBM RACF JES(BATCHALLRACF) SETROPTS value must be set to JES(BATCHALLRACF). |
In certain situations, software applications/programs need to execute with elevated privileges to perform required functions. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications/programs, those users are indirectly provided with greater privileges than assigned by the organizations.... |
|
V-223691
|
Medium |
The IBM z/OS IEASYMUP resource must be protected in accordance with proper security requirements. |
Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. |
|
V-223690
|
Medium |
IBM RACF must limit WRITE or greater access to the JES2 System data sets (e.g., Spool, Checkpoint, and Initialization parameters) to system programmers only. |
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... |
|
V-223689
|
Medium |
IBM z/OS MCS consoles access authorization(s) for CONSOLE resource(s) must be properly protected. |
MCS 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.
Preventing non-privileged users from... |
|
V-223688
|
Medium |
IBM RACF must limit access to System page data sets (i.e., PLPA, COMMON, and LOCALx) to system programmers. |
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... |
|
V-223686
|
Medium |
IBM RACF 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. |
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... |
|
V-223683
|
Medium |
IBM RACF access to SYS1.LINKLIB must be properly protected. |
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... |
|
V-223681
|
Medium |
IBM RACF must limit access to SYSTEM DUMP data sets to system programmers only. |
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... |
|
V-223680
|
Medium |
IBM RACF must limit WRITE or greater access to all system-level product installation libraries to system programmers. |
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... |
|
V-223673
|
Medium |
IBM RACF batch jobs must be protected with propagation control. |
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... |
|
V-223672
|
Medium |
IBM RACF batch jobs must be properly secured. |
Batch jobs that are submitted to the operating system should inherit the USERID of the submitter. This will identify the batch job with a userid for the purpose of accessing resources. BATCHALLRACF ensures that a valid USERID is associated with batch jobs. Jobs that are submitted to the operating system... |
|
V-223671
|
Medium |
IBM RACF must limit access to SYS(x).TRACE to system programmers only. |
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... |
|
V-223670
|
Medium |
IBM RACF must limit WRITE or greater access to System backup files to system programmers and/or batch jobs that perform DASD backups. |
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... |
|
V-223669
|
Medium |
IBM RACF allocate access to system user catalogs must be properly protected. |
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... |
|
V-223665
|
Medium |
IBM RACF Global Access Checking must be restricted to appropriate classes and resources. |
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... |
|
V-223664
|
Medium |
IBM Sensitive Utility Controls must be properly defined and protected. |
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... |
|
V-223663
|
Medium |
IBM RACF DASD volume-level protection must be properly defined. |
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... |
|
V-223662
|
Medium |
IBM RACF USERIDs possessing the Tape Bypass Label Processing (BLP) privilege must be justified. |
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... |
|
V-223661
|
Medium |
IBM RACF started tasks defined with the trusted attribute must be justified. |
Trusted Started tasks bypass RACF checking. It is vital that this attribute is NOT granted to unauthorized Started Tasks which could then obtain unauthorized access to the system. This could result in the compromise of the confidentiality, integrity, and availability of the operating system, ACP, or customer data. |
|
V-223660
|
Medium |
IBM RACF CLASSACT SETROPTS must be specified for the TEMPDSN class. |
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... |
|
V-223659
|
Medium |
The IBM RACF MCS consoles resource class must be active. |
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... |
|
V-223658
|
Medium |
The IBM RACF OPERCMDS resource class must be active. |
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... |
|
V-223657
|
Medium |
The IBM RACF FACILITY resource class must be active. |
IBM Provides the FACILITY Class for use in protecting a variety of features/functions/products both IBM and third-party. The FACILITY Class is not dedicated to any one specific use and is intended as a multi-purpose RACF Class. Failure to activate this class will result in unprotected resources. This exposure may threaten... |
|
V-223656
|
Medium |
IBM RACF must properly define users that have access to the CONSOLE resource in the TSOAUTH resource class. |
MCS 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. |
|
V-223655
|
Medium |
IBM z/OS system commands must be properly protected. |
z/OS system commands provide a method of controlling the operating environment. Failure to properly control access to z/OS system commands could result in unauthorized personnel issuing sensitive system commands. This exposure may threaten the integrity and availability of the operating system environment, and compromise the confidentiality of customer data. |
|
V-223654
|
Medium |
IBM RACF must protect memory and privileged program dumps in accordance with proper security requirements. |
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... |
|
V-223653
|
Medium |
IBM RACF SETROPTS LOGOPTIONS must be properly configured. |
Once an attacker establishes access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create an account. Auditing account creation actions provides logging that can be used for forensic purposes.
To address access requirements,... |
|
V-223652
|
Medium |
IBM RACF emergency USERIDs must be properly defined. |
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... |
|
V-223648
|
Medium |
All digital certificates in use must have a valid path to a trusted certification authority (CA). |
The origin of a certificate, or the CA, is crucial in determining if the certificate should be trusted. An approved CA establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted.
Satisfies: SRG-OS-000066-GPOS-00034, SRG-OS-000403-GPOS-00182 |
|
V-223647
|
Medium |
Expired digital certificates must not be used. |
The longer and more often a key is used, the more susceptible it is to loss or discovery. This weakens the assurance provided to a relying Party that the unique binding between a key and its named subscriber is valid. Therefore, it is important that certificates are periodically refreshed. This... |
|
V-223646
|
Medium |
Certificate Name Filtering must be implemented with appropriate authorization and documentation. |
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational 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)... |
|
V-223787
|
Low |
IBM z/OS must not have duplicated sensitive utilities and/or programs existing in APF libraries. |
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. |
|
V-223650
|
Low |
IBM RACF must limit Write or greater access to libraries that contain PPT modules to system programmers only. |
Specific PPT designated program modules possess significant security bypass capabilities. Unauthorized access could result in the compromise of the operating system environment, ACP, and customer data.
Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000259-GPOS-00100, SRG-OS-000324-GPOS-00125 |
