DoD Compliance · STIG

IBM zVM Using CA VM:Secure Security Technical Implementation Guide

V2R1 · · 4.8 years ago · Released 23 Jul 2021 · 77 rules

Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Digest of Updates vs. V1R2 · 27 Apr 2018 +77 −77

Comparison against the immediately-prior release (V1R2). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Added rules 77

V-237897 High CA VM:Secure product Rules Facility must be installed and operating.
V-237898 High The IBM z/VM TCP/IP DTCPARMS files must be properly configured to connect to an external security manager.
V-237899 Medium CA VM:Secure product must be installed and operating.
V-237900 Medium The IBM z/VM JOURNALING LOGON parameter must be set for lockout after 3 attempts for 15 minutes.
V-237901 Medium The CA VM:Secure JOURNAL Facility parameters must be set for lockout after 3 attempts.
V-237902 Medium The IBM z/VM LOGO Configuration file must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system.
V-237903 Medium The IBM z/VM TCP/IP FTP Server must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system and until users acknowledge the usage conditions and take explicit actions to log on for further access.
V-237904 Medium The IBM z/VM LOGO configuration file must be configured to display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access.
V-237905 Medium For FTP processing Z/VM TCP/IP FTP server Exit must be enabled.
V-237906 Medium The IBM z/VM TCP/IP configuration must include an SSLSERVERID statement.
V-237907 Medium CA VM:Secure product AUDIT file must be restricted to authorized personnel.
V-237908 Medium The IBM z/VM Journal option must be specified in the Product Configuration File.
V-237909 Medium All digital certificates in use must have a valid path to a trusted Certification authority.
V-237910 Medium The IBM z/VM TCP/IP Key database for LDAP or SSL server must be created with the proper permissions.
V-237911 High CA VM:Secure product Password Encryption (PEF) option must be properly configured to store and transmit cryptographically-protected passwords.
V-237912 Medium CA VM:Secure product AUTOEXP record in the Security Config File must be properly set.
V-237913 Medium CA VM:Secure product PASSWORD user exit must be coded with the PWLIST option properly set.
V-237914 Medium IBM zVM CA VM:Secure product PASSWORD user exit must be in use.
V-237915 Medium IBM z/VM must be configured to disable non-essential capabilities.
V-237916 Medium CA VM:Secure product Config Delay LOG option must be set to 0.
V-237917 Medium CA VM:Secure product NORULE record in the SECURITY CONFIG file must be configured to REJECT.
V-237918 Medium All IBM z/VM TCP/IP Ports must be restricted to ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
V-237919 Medium The IBM z/VM Security Manager must provide a procedure to disable userIDs after 35 days of inactivity.
V-237920 High The IBM z/VM TCP/IP VMSSL command operands must be configured properly.
V-237921 Medium The IBM z/VM TCP/IP ANONYMOU statement must not be coded in FTP configuration.
V-237922 Medium CA VM:Secure product ADMIN GLOBALS command must be restricted to systems programming personnel.
V-237923 Medium CA VM:Secure must have a security group for Security Administrators only.
V-237924 Medium The IBM z/VM SYSTEM CONFIG file must be configured to clear TDISK on IPL.
V-237925 Medium The IBM z/VM TCP/IP FOREIGNIPCONLIMIT statement must be properly configured.
V-237926 Medium The IBM z/VM TCP/IP PERSISTCONNECTIONLIMIT statement must be properly configured.
V-237927 Medium The IBM z/VM TCP/IP PENDINGCONNECTIONLIMIT statement must be properly configured.
V-237928 Medium IBM z/VM tapes must use Tape Encryption.
V-237929 Medium The IBM z/VM TCP/IP must be configured to display the mandatory DoD Notice and Consent banner before granting access to the system.
V-237930 Medium The IBM z/VM JOURNALING statement must be coded on the configuration file.
V-237931 Medium CA VM:Secure product SECURITY CONFIG file must be restricted to appropriate personnel.
V-237932 Medium The IBM z/VM AUDT and Journal Mini Disks must be restricted to the appropriate system administrators.
V-237933 Medium IBM z/VM must remove or disable emergency accounts after the crisis is resolved or 72 hours.
V-237934 Medium The IBM z/VM must restrict link access to the disk on which system software resides.
V-237935 Medium The IBM z/VM Privilege command class A and Class B must be properly assigned.
V-237936 Medium CA VM:Secure AUTHORIZ CONFIG file must be properly configured.
V-237937 Medium The IBM z/VM journal minidisk space allocation must be large enough for one weeks worth of audit records.
V-237938 Medium CA VM:Secure product audit records must offload audit records to a different system or media.
V-237939 Medium CA VM:Secure product audit records must be offloaded on a weekly basis.
V-237940 Medium The IBM z/VM Portmapper server virtual machine userID must be included in the AUTOLOG statement of the TCP/IP server configuration file.
V-237941 Medium CA VM:Secure product MANAGE command must be restricted to system administrators.
V-237942 Medium The CA VM:Secure LOGONBY command must be restricted to system administrators.
V-237943 Medium The IBM z/VM CP Privilege Class A, B, and D must be restricted to appropriate system operators.
V-237944 Medium The IBM z/VM JOURNALING statement must be properly configured.
V-237945 Medium The IBM z/VM TCP/IP SECUREDATA option for FTP must be set to REQUIRED.
V-237946 Medium IBM z/VM TCP/IP config file INTERNALCLIENTPARMS statement must be properly configured.
V-237947 Medium All IBM z/VM TCP/IP servers must be configured for SSL/TLS connection.
V-237948 Medium The IBM z/VM TCP/IP SECURETELNETCLIENT option for telnet must be set to YES.
V-237954 Medium The IBM z/VM Privilege Classes C and E must be restricted to appropriate system administrators.
V-237955 Medium The IBM z/VM Privilege Class F must be restricted to service representatives and system administrators only.
V-237956 Medium The IBM z/VM ANY Privilege Class must not be listed for privilege commands.
V-237957 Medium CA VM:Secure product VMXRPI configuration file must be restricted to authorized personnel.
V-237958 Medium CA VM:Secure product DASD CONFIG file must be restricted to appropriate personnel.
V-237959 Medium CA VM:Secure product AUTHORIZ CONFIG file must be restricted to appropriate personnel.
V-237960 Medium CA VM:Secure product CONFIG file must be restricted to appropriate personnel.
V-237961 Medium CA VM:Secure Product SFS configuration file must be restricted to appropriate personnel.
V-237962 Medium CA VM:Secure product Rules Facility must be restricted to appropriate personnel.
V-237963 Medium IBM z/VM must employ a Session manager.
V-237964 Medium The IBM z/VM System administrator must develop a notification routine for account management.
V-237965 Medium The IBM z/VM system administrator must develop routines and processes for the proper configuration and maintenance of Software.
V-237966 Medium IBM z/VM must be protected by an external firewall that has a deny-all, allow-by-exception policy.
V-237967 Medium The IBM z/VM System administrator must develop routines and processes for notification in the event of audit failure.
V-237968 Medium The IBM z/VM system administrator must develop procedures maintaining information system operation in the event of anomalies.
V-237969 Medium IBM z/VM system administrator must develop procedures to manually control temporary, interactive, and emergency accounts.
V-237970 Medium IBM z/VM must have access to an audit reduction tool that allows for central data review and analysis.
V-237971 Medium The IBM z/VM system administrator must develop and perform a procedure to validate the correct operation of security functions.
V-237972 Medium IBM z/VM must employ Clock synchronization software.
V-237973 Medium The IBM z/VM systems requiring data at rest must employ IBMs DS8000 for full disk encryption.
V-245530 Medium The IBM z/VM TCP/IP NSLOOKUP statement for UFT servers must be properly configured.
V-245531 Medium The IBM z/VM TCP/IP DOMAINLOOKUP statement must be properly configured.
V-245532 Medium The IBM z/VM TCP/IP NSINTERADDR statement must be present in the TCPIP DATA configuration.
V-245533 Medium The IBM z/VM CHECKSUM statement must be included in the TCP/IP configuration file.
V-245534 Medium The IBM z/VM DOMAINSEARCH statement in the TCPIP DATA file must be configured with proper domain names for name resolution.

Removed rules 77

V-78841 High CA VM:Secure product Rules Facility must be installed and operating.
V-78843 High The IBM z/VM TCP/IP DTCPARMS files must be properly configured to connect to an external security manager.
V-78845 Medium CA VM:Secure product must be installed and operating.
V-78847 Medium The IBM z/VM JOURNALING LOGON parameter must be set for lockout after 3 attempts for 15 minutes.
V-78849 Medium The CA VM:Secure JOURNAL Facility parameters must be set for lockout after 3 attempts.
V-78851 Medium The IBM z/VM LOGO Configuration file must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system.
V-78853 Medium The IBM z/VM TCP/IP FTP Server must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system and until users acknowledge the usage conditions and take explicit actions to log on for further access.
V-78855 Medium The IBM z/VM LOGO configuration file must be configured to display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access.
V-78857 Medium For FTP processing Z/VM TCP/IP FTP server Exit must be enabled.
V-78859 Medium The IBM z/VM TCP/IP configuration must include an SSLSERVERID statement.
V-78861 Medium CA VM:Secure product AUDIT file must be restricted to authorized personnel.
V-78863 Medium The IBM z/VM Journal option must be specified in the Product Configuration File.
V-78865 Medium All digital certificates in use must have a valid path to a trusted Certification authority.
V-78867 Medium The IBM z/VM TCP/IP Key database for LDAP or SSL server must be created with the proper permissions.
V-78869 High CA VM:Secure product Password Encryption (PEF) option must be properly configured to store and transmit cryptographically-protected passwords.
V-78871 Medium CA VM:Secure product AUTOEXP record in the Security Config File must be properly set.
V-78873 Medium CA VM:Secure product PASSWORD user exit must be coded with the PWLIST option properly set.
V-78875 Medium IBM zVM CA VM:Secure product PASSWORD user exit must be in use.
V-78877 Medium IBM z/VM must be configured to disable non-essential capabilities.
V-78879 Medium CA VM:Secure product Config Delay LOG option must be set to 0.
V-78881 Medium CA VM:Secure product NORULE record in the SECURITY CONFIG file must be configured to REJECT.
V-78883 Medium All IBM z/VM TCP/IP Ports must be restricted to ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
V-78885 Medium The IBM z/VM Security Manager must provide a procedure to disable userIDs after 35 days of inactivity.
V-78887 High The IBM z/VM TCP/IP VMSSL command operands must be configured properly.
V-78889 Medium The IBM z/VM TCP/IP ANONYMOU statement must not be coded in FTP configuration.
V-78891 Medium CA VM:Secure product ADMIN GLOBALS command must be restricted to systems programming personnel.
V-78893 Medium CA VM:Secure must have a security group for Security Administrators only.
V-78895 Medium The IBM z/VM SYSTEM CONFIG file must be configured to clear TDISK on IPL.
V-78897 Medium The IBM z/VM TCP/IP FOREIGNIPCONLIMIT statement must be properly configured.
V-78899 Medium The IBM z/VM TCP/IP PERSISTCONNECTIONLIMIT statement must be properly configured.
V-78901 Medium The IBM z/VM TCP/IP PENDINGCONNECTIONLIMIT statement must be properly configured.
V-78903 Medium IBM z/VM tapes must use Tape Encryption.
V-78905 Medium The IBM z/VM TCP/IP must be configured to display the mandatory DoD Notice and Consent banner before granting access to the system.
V-78907 Medium The IBM z/VM JOURNALING statement must be coded on the configuration file.
V-78909 Medium CA VM:Secure product SECURITY CONFIG file must be restricted to appropriate personnel.
V-78911 Medium The IBM z/VM AUDT and Journal Mini Disks must be restricted to the appropriate system administrators.
V-78913 Medium IBM z/VM must remove or disable emergency accounts after the crisis is resolved or 72 hours.
V-78915 Medium The IBM z/VM must restrict link access to the disk on which system software resides.
V-78917 Medium The IBM z/VM Privilege command class A and Class B must be properly assigned.
V-78919 Medium CA VM:Secure AUTHORIZ CONFIG file must be properly configured.
V-78921 Medium The IBM z/VM journal minidisk space allocation must be large enough for one weeks worth of audit records.
V-78923 Medium CA VM:Secure product audit records must offload audit records to a different system or media.
V-78925 Medium CA VM:Secure product audit records must be offloaded on a weekly basis.
V-78927 Medium The IBM z/VM Portmapper server virtual machine userID must be included in the AUTOLOG statement of the TCP/IP server configuration file.
V-78929 Medium CA VM:Secure product MANAGE command must be restricted to system administrators.
V-78931 Medium The CA VM:Secure LOGONBY command must be restricted to system administrators.
V-78933 Medium The IBM z/VM CP Privilege Class A, B, and D must be restricted to appropriate system operators.
V-78935 Medium The IBM z/VM JOURNALING statement must be properly configured.
V-78937 Medium The IBM z/VM TCP/IP SECUREDATA option for FTP must be set to REQUIRED.
V-78939 Medium IBM z/VM TCP/IP config file INTERNALCLIENTPARMS statement must be properly configured.
V-78941 Medium All IBM z/VM TCP/IP servers must be configured for SSL/TLS connection.
V-78943 Medium The IBM z/VM TCP/IP SECURETELNETCLIENT option for telnet must be set to YES.
V-78945 Medium The IBM z/VM TCP/IP NSLOOKUP statement for UFT servers must be properly configured.
V-78947 Medium The IBM z/VM TCP/IP DOMAINLOOKUP statement must be properly configured.
V-78949 Medium The IBM z/VM TCP/IP NSINTERADDR statement must be present in the TCPIP DATA configuration.
V-78951 Medium The IBM z/VM CHECKSUM statement must be included in the TCP/IP configuration file.
V-78953 Medium The IBM z/VM DOMAINSEARCH statement in the TCPIP DATA file must be configured with proper domain names for name resolution.
V-78955 Medium The IBM z/VM Privilege Classes C and E must be restricted to appropriate system administrators.
V-78957 Medium The IBM z/VM Privilege Class F must be restricted to service representatives and system administrators only.
V-78959 Medium The IBM z/VM ANY Privilege Class must not be listed for privilege commands.
V-78961 Medium CA VM:Secure product VMXRPI configuration file must be restricted to authorized personnel.
V-78963 Medium CA VM:Secure product DASD CONFIG file must be restricted to appropriate personnel.
V-78965 Medium CA VM:Secure product AUTHORIZ CONFIG file must be restricted to appropriate personnel.
V-78967 Medium CA VM:Secure product CONFIG file must be restricted to appropriate personnel.
V-78969 Medium CA VM:Secure Product SFS configuration file must be restricted to appropriate personnel.
V-78971 Medium CA VM:Secure product Rules Facility must be restricted to appropriate personnel.
V-78973 Medium IBM z/VM must employ a Session manager.
V-78975 Medium The IBM z/VM System administrator must develop a notification routine for account management.
V-78977 Medium The IBM z/VM system administrator must develop routines and processes for the proper configuration and maintenance of Software.
V-78979 Medium IBM z/VM must be protected by an external firewall that has a deny-all, allow-by-exception policy.
V-78981 Medium The IBM z/VM System administrator must develop routines and processes for notification in the event of audit failure.
V-78983 Medium The IBM z/VM system administrator must develop procedures maintaining information system operation in the event of anomalies.
V-78985 Medium IBM z/VM system administrator must develop procedures to manually control temporary, interactive, and emergency accounts.
V-78987 Medium IBM z/VM must have access to an audit reduction tool that allows for central data review and analysis.
V-78989 Medium The IBM z/VM system administrator must develop and perform a procedure to validate the correct operation of security functions.
V-78991 Medium IBM z/VM must employ Clock synchronization software.
V-78993 Medium The IBM z/VM systems requiring data at rest must employ IBMs DS8000 for full disk encryption.

Sort by

Expand all

CA VM:Secure product Rules Facility must be installed and operating.

AC-2 - High - CCI-000015 - V-237897 - SV-237897r649531_rule

RMF Control

AC-2

Severity

CCI

CCI-000015

Version

IBMZ-VM-000010

Vuln IDs

V-237897
V-78841

Rule IDs

SV-237897r649531_rule
SV-93547

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/VM requires an external security manager to assure proper account management. Satisfies: SRG-OS-000001-GPOS-00001, SRG-OS-000080-GPOS-00048

Checks: C-41107r649529_chk

Verify an “ACCESS RULE” record exists on the system using the following command: VMSECURE CONFIG PRODUCT If there is no “ACCESS RULE” record, this is a finding. Verify that CA VM:SECURE RULES can be added using the following command: VMSECURE RULES USER If a rules file does not open, this is a finding.

Fix: F-41066r649530_fix

Ensure the Rules Facility is installed and the Product Config file contains an “ACCESS RULES” statement.

The IBM z/VM TCP/IP DTCPARMS files must be properly configured to connect to an external security manager.

AC-2 - High - CCI-000015 - V-237898 - SV-237898r649534_rule

RMF Control

AC-2

Severity

CCI

CCI-000015

Version

IBMZ-VM-000020

Vuln IDs

V-237898
V-78843

Rule IDs

SV-237898r649534_rule
SV-93549

A comprehensive account management process such as provided by External Security Managers (ESM) which includes automation helps to ensure accounts designated as requiring attention are consistently and promptly addressed. Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended, or terminated, or by disabling accounts located in non-centralized account stores such as multiple servers. This requirement applies to all account types, including individual/user, shared, group, system, guest/anonymous, emergency, developer/manufacturer/vendor, temporary, and service. DTCPARMS setting assures that an ESM is enabled. Account management functions include: assigning group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts.

Checks: C-41108r649532_chk

Determine location of “DTCPARMS” File for each of the following installed servers: FTP (FTPSERVE) IMAP (IMAP) NFS (VMNFS) REXEC (REXECD) If each “DTCPARMS” file includes the following statements, this is not a finding. :ESM_Enable.YES :ESM_Racroute.YES (or a valid exit name) :ESM_Validate.YES (or a valid exit name)

Fix: F-41067r649533_fix

For each of the following installed severs: FTP (FTPSERVE) IMAP (IMAP) NFS (VMNFS) REXEC (REXECD) Configure the DTCPARMS file in the TCP/IP configuration to include the following statements: :ESM_Enable.YES :ESM_Racroute.YES (or a valid exit name) :ESM_Validate.YES (or a valid exit name)

CA VM:Secure product must be installed and operating.

AC-2 - Medium - CCI-000018 - V-237899 - SV-237899r649537_rule

RMF Control

AC-2

Severity

CCI

CCI-000018

Version

IBMZ-VM-000030

Vuln IDs

V-237899
V-78845

Rule IDs

SV-237899r649537_rule
SV-93551

A comprehensive account management process such as provided by an External Security Manager (ESM) which includes automation helps to ensure accounts designated as requiring attention are consistently and promptly addressed. Account management functions include: assigning group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. 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. Satisfies: SRG-OS-000004-GPOS-00004, SRG-OS-000032-GPOS-00013, SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00020, SRG-OS-000042-GPOS-00021, SRG-OS-000062-GPOS-00031, SRG-OS-000255-GPOS-00096, SRG-OS-000365-GPOS-00152, SRG-OS-000327-GPOS-00127, SRG-OS-000462-GPOS-00206, SRG-OS-000064-GPOS-00033, SRG-OS-000458-GPOS-00203, SRG-OS-000461-GPOS-00205, SRG-OS-000463-GPOS-00207, SRG-OS-000303-GPOS-00120, SRG-OS-000466-GPOS-00210, SRG-OS-000467-GPOS-00211, SRG-OS-000468-GPOS-00212, SRG-OS-000471-GPOS-00215, SRG-OS-000471-GPOS-00216, SRG-OS-000472-GPOS-00217, SRG-OS-000473-GPOS-00218, SRG-OS-000474-GPOS-00219, SRG-OS-000475-GPOS-00220, SRG-OS-000476-GPOS-00221, SRG-OS-000477-GPOS-00222, SRG-OS-000240-GPOS-00090, SRG-OS-000241-GPOS-00091, SRG-OS-000392-GPOS-00172, SRG-OS-000239-GPOS-00089, SRG-OS-000465-GPOS-00209

Checks: C-41109r649535_chk

Verify the CA VM:Secure product is operational on the system by entering the following command. From the “CMS” command line enter: VMSECURE VERSION If there is no response, "VMSECURE" is not logged in, this is a finding.

Fix: F-41068r649536_fix

CA VM:Secure product audits all commands. Ensure CA VM:Secure product is installed and operational. Using CA VM:Secure product audit of all commands with z/VM standard journal record assures that all pertinent information is stored.

The IBM z/VM JOURNALING LOGON parameter must be set for lockout after 3 attempts for 15 minutes.

AC-7 - Medium - CCI-000044 - V-237900 - SV-237900r649540_rule

RMF Control

AC-7

Severity

CCI

CCI-000044

Version

IBMZ-VM-000040

Vuln IDs

V-237900
V-78847

Rule IDs

SV-237900r649540_rule
SV-93553

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.

Checks: C-41110r649538_chk

Display the System Configuration File. If the “JOURNALING” statement is set to: Facility ON LOGON Lockout after 3 attempts for 15 minutes, this is not a finding. Note: Site may set Lockout value at 0, this will require system administrator action for reset. Issue "QUERY JOURNAL" command. If the response is as follows this is not a finding: Journal: LOGON-on

Fix: F-41069r649539_fix

Configure the System Configuration “JOURNALING” statement to: Facility ON LOGON Lockout after 3 attempts for 15 minutes or 0 if system administrator action is desired.

The CA VM:Secure JOURNAL Facility parameters must be set for lockout after 3 attempts.

AC-7 - Medium - CCI-000044 - V-237901 - SV-237901r649543_rule

RMF Control

AC-7

Severity

CCI

CCI-000044

Version

IBMZ-VM-000045

Vuln IDs

V-237901
V-78849

Rule IDs

SV-237901r649543_rule
SV-93555

Checks: C-41111r649541_chk

Examine VM:Secure Security Config File. If there is no Journal record this is a finding. If the Journal record has a maximum consecutive invalid password attempts set to 3, this is not a finding. Note: The "warning" setting may be determined by the site but must be 3 or less. Example: JOURNAL 3 3

Fix: F-41070r649542_fix

Edit the SECURITY CONFIG file: vmsecure config security Configure a JOURNAL record in the SECURITY CONFIG file as follows: JOURNAL 3 3 Note: The "warning" setting may be determined by the site but must be 3 or less.

The IBM z/VM LOGO Configuration file must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system.

AC-8 - Medium - CCI-000048 - V-237902 - SV-237902r649546_rule

RMF Control

AC-8

Severity

CCI

CCI-000048

Version

IBMZ-VM-000050

Vuln IDs

V-237902
V-78851

Rule IDs

SV-237902r649546_rule
SV-93557

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. 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. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

Checks: C-41112r649544_chk

Display the System Configuration file “LOGO_Config” statement. Determine the file name and file type of a LOGO configuration file. For each LOGO file Identified: If the file contains the following logon banner, this is not a finding. The below banner is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. If all the items above are true, this is not finding. If any item above is untrue, this is a finding.

Fix: F-41071r649545_fix

Configure files identified by the System Configuration file “LOGO_Config” statement to point to a file containing the following Banner. The banner below is mandatory and deviations are not permitted except as authorized in writing by the DoD Chief Information Officer. The thrust of this new policy is to make it clear that there is no expectation of privacy when using DoD information systems and all use of DoD information systems is subject to searching, auditing, inspecting, seizing, and monitoring, even if some personal use of a system is permitted: STANDARD MANDATORY DOD NOTICE AND CONSENT BANNER You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.

The IBM z/VM TCP/IP FTP Server must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting local or remote access to the system and until users acknowledge the usage conditions and take explicit actions to log on for further access.

AC-8 - Medium - CCI-000048 - V-237903 - SV-237903r649549_rule

RMF Control

AC-8

Severity

CCI

CCI-000048

Version

IBMZ-VM-000060

Vuln IDs

V-237903
V-78853

Rule IDs

SV-237903r649549_rule
SV-93559

The banner must be acknowledged by the user prior to allowing the user access to the operating system. This provides assurance that the user has seen the message and accepted the conditions for access. If the consent banner is not acknowledged by the user, DoD will not be in compliance with system use notifications required by law. To establish acceptance of the application usage policy, a click-through banner at system logon is required. The system must prevent further activity until the user executes a positive action to manifest agreement by clicking on a box indicating "OK". Satisfies: SRG-OS-000023-GPOS-00006, SRG-OS-000024-GPOS-00007

Checks: C-41113r649547_chk

Examine the CMS search order. Verify the FTP Server access to a FTP BANNER file. If there is no accessible FTP BANNER file, this is a finding. Ensure that the “FTP Banner” file contains the following: The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." If it does not, this is a finding.

Fix: F-41072r649548_fix

Configure the “FTP Banner” file to contain the following: The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

The IBM z/VM LOGO configuration file must be configured to display the Standard Mandatory DoD Notice and Consent Banner until users acknowledge the usage conditions and take explicit actions to log on for further access.

AC-8 - Medium - CCI-000050 - V-237904 - SV-237904r649552_rule

RMF Control

AC-8

Severity

CCI

CCI-000050

Version

IBMZ-VM-000070

Vuln IDs

V-237904
V-78855

Rule IDs

SV-237904r649552_rule
SV-93561

Checks: C-41114r649550_chk

Examine the “LOGO_CONFIG” settings for the file name of the logo configuration file. Ensure that the file name indicated in the statement contains the DoD official Logon Banner. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't." If it does not, this is a finding. If any item above is untrue, this is a finding.

Fix: F-41073r649551_fix

Configure the “LOGO_CONFIG” statement to indicate a file that contains the DoD Standard Banner. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

For FTP processing Z/VM TCP/IP FTP server Exit must be enabled.

AC-17 - Medium - CCI-000067 - V-237905 - SV-237905r649555_rule

RMF Control

AC-17

Severity

CCI

CCI-000067

Version

IBMZ-VM-000090

Vuln IDs

V-237905
V-78857

Rule IDs

SV-237905r649555_rule
SV-93563

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 an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.

Checks: C-41115r649553_chk

If there are no FTP servers’ active, this is not applicable. Issue “SMSG” command for each FTP Server. Query “FTAUDIT”. If the “Exit” is not enabled, this is a finding.

Fix: F-41074r649554_fix

Include the “FTAUDIT” statement in the TCP/IP Configuration file.

The IBM z/VM TCP/IP configuration must include an SSLSERVERID statement.

AC-17 - Medium - CCI-000068 - V-237906 - SV-237906r649558_rule

RMF Control

AC-17

Severity

CCI

CCI-000068

Version

IBMZ-VM-000110

Vuln IDs

V-237906
V-78859

Rule IDs

SV-237906r649558_rule
SV-93565

The Secure Socket Layer (SSL) server, provides processing support for secure (encrypted) communication between remote clients and z/VM TCP/IP application servers that are configured for secure communications The TCP/IP (stack) server routes requests for secure connections to an SSL server, which interacts with a client on behalf of an application server to perform handshake operations and the exchange of cryptographic parameters for a secure session. The SSL server then manages the encryption and decryption of data for an established, secure session. Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information. Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Satisfies: SRG-OS-000033-GPOS-00014, SRG-OS-000250-GPOS-00093, SRG-OS-000424-GPOS-00188, SRG-OS-000426-GPOS-00190, SRG-OS-000393-GPOS-00173, SRG-OS-000394-GPOS-00174, SRG-OS-000423-GPOS-00187

Checks: C-41116r649556_chk

Examine the “SSLSERVERID” statement in the TCP/IP server configuration file. If the “SSLSERVERID” statement identifies at least one userID for an SSL server, this is not a finding.

Fix: F-41075r649557_fix

Configure the “SSLSERVERID” statement to force auto logging of an SSL server before all other servers in the “AUTOLOG” list.

CA VM:Secure product AUDIT file must be restricted to authorized personnel.

AU-9 - Medium - CCI-000162 - V-237907 - SV-237907r649561_rule

RMF Control

AU-9

Severity

CCI

CCI-000162

Version

IBMZ-VM-000190

Vuln IDs

V-237907
V-78861

Rule IDs

SV-237907r649561_rule
SV-93567

Unauthorized disclosure of audit records can reveal system and configuration data to attackers, thus compromising its confidentiality. Audit information includes all information (e.g., audit records, audit settings, audit reports) needed to successfully audit operating system activity. Satisfies: SRG-OS-000057-GPOS-00027, SRG-OS-000058-GPOS-00028, SRG-OS-000059-GPOS-00029

Checks: C-41117r649559_chk

Determine the VMSECURE Audit disk. Note: Consult the z/VM system administrator for this information. Review all rules that grant access to the identified VM:Secure AUDIT disk. If any grant access to anyone other than a system administrator or security administrator, this is a finding.

Fix: F-41076r649560_fix

Ensure access to VMSECURE AUDIT disk is restricted to system administrators or security administrators.

The IBM z/VM Journal option must be specified in the Product Configuration File.

AU-12 - Medium - CCI-000172 - V-237908 - SV-237908r649564_rule

RMF Control

AU-12

Severity

CCI

CCI-000172

Version

IBMZ-VM-000320

Vuln IDs

V-237908
V-78863

Rule IDs

SV-237908r649564_rule
SV-93569

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., module or policy filter). The JOURNALING statement tells z/VM CP to include the journaling facility and to enable the system being initialized to set and query the journaling facility.

Checks: C-41118r649562_chk

Examine the “Product Configuration” file. If the JOURNALING Statement does not specify “ON”, this is a finding.

Fix: F-41077r649563_fix

Configure the Product Configuration files’ JOURNALING statement to “JOURNALING ON”.

All digital certificates in use must have a valid path to a trusted Certification authority.

IA-5 - Medium - CCI-000185 - V-237909 - SV-237909r649567_rule

RMF Control

IA-5

Severity

CCI

CCI-000185

Version

IBMZ-VM-000460

Vuln IDs

V-237909
V-78865

Rule IDs

SV-237909r649567_rule
SV-93571

Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC. When there is a chain of trust, usually the top entity to be trusted becomes the trust anchor; it can be, for example, a Certification Authority (CA). A certification path starts with the subject certificate and proceeds through a number of intermediate certificates up to a trusted root certificate, typically issued by a trusted CA. This requirement verifies that a certification path to an accepted trust anchor is used for certificate validation and that the path includes status information. Path validation is necessary for a relying party to make an informed trust decision when presented with any certificate not already explicitly trusted. Status information for certification paths includes certificate revocation lists or online certificate status protocol responses. Validation of the certificate status information is out of scope for this requirement.

Checks: C-41119r649565_chk

Invoke the “gskkyman” utility. From the “Key Management” Menu display Certificate Information. If no certificate information is found, this is not a finding. Note: Certificates are only valid when their status is “TRUST”. Therefore, you may ignore certificates with the “NOTRUST” status during the following checks. If the digital certificate information indicates that the issuer's distinguished name leads to a DoD PKI Root Certificate Authority or External Certification Authority (ECA), this is not a finding. Reference the IASE website for complete information as to which certificates are acceptable (http://iase.disa.mil/pki-pke/interoperability/).

Fix: F-41078r649566_fix

Remove or and replace certificates whose issuer's distinguished name does not lead to a DoD PKI Root Certification Authority, External Root Certification Authority (ECA), or an approved External Partner PKI’s Root Certification Authority.

The IBM z/VM TCP/IP Key database for LDAP or SSL server must be created with the proper permissions.

IA-5 - Medium - CCI-000186 - V-237910 - SV-237910r649570_rule

RMF Control

IA-5

Severity

CCI

CCI-000186

Version

IBMZ-VM-000470

Vuln IDs

V-237910
V-78867

Rule IDs

SV-237910r649570_rule
SV-93573

If the private key is discovered, an attacker can use the key to authenticate as an authorized user and gain access to the network infrastructure. The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and non-repudiation gained through PKI because the attacker can use the private key to digitally sign documents and pretend to be the authorized user. Both the holders of a digital certificate and the issuing authority must protect the computers, storage devices, or whatever they use to keep the private keys.

Checks: C-41120r649568_chk

Issue command openvm list /etc./gskadm/ (own) If the file permissions are as displayed below, this is not a finding. User ID Group Name Permissions Type Path name component gskadmin security rw- r-- --- F ’Database.kdb’ gskadmin security rw- --- --- F ’Database.rdb’ gskadmin security rw- r-- --- F ’Database.sth’

Fix: F-41079r649569_fix

Ensure proper permissions are assigned to Key databases. Issue the “OPENVM PERMIT” commands to assign proper permissions.

CA VM:Secure product Password Encryption (PEF) option must be properly configured to store and transmit cryptographically-protected passwords.

IA-5 - High - CCI-000196 - V-237911 - SV-237911r649573_rule

RMF Control

IA-5

Severity

CCI

CCI-000196

Version

IBMZ-VM-000480

Vuln IDs

V-237911
V-78869

Rule IDs

SV-237911r649573_rule
SV-93575

Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised. Satisfies: SRG-OS-000073-GPOS-00041, SRG-OS-000074-GPOS-00042

Checks: C-41121r649571_chk

Examine the “VMXRPI” Config file used for building the current nucleus. If the “ENCRYP” record is missing, this is a finding. If the “ENCRYPT” record does not specify “DES3”, this is a finding. If the DES3KEY Record is missing, this is a finding.

Fix: F-41080r649572_fix

Configure the “VMXRPI” Config file to include the following records: ENCRYPT DES3 DES3KEY word1 word2 word3 word4 word5 word6 or DES3KEY EXIT filename EXEC|TEXT

CA VM:Secure product AUTOEXP record in the Security Config File must be properly set.

IA-5 - Medium - CCI-000199 - V-237912 - SV-237912r649576_rule

RMF Control

IA-5

Severity

CCI

CCI-000199

Version

IBMZ-VM-000500

Vuln IDs

V-237912
V-78871

Rule IDs

SV-237912r649576_rule
SV-93577

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.

Checks: C-41122r649574_chk

Examine the “SECURITY CONFIG” file. If there is no “AUTOEXP” record, this is a finding. If the “AUTOEXP” record is configured as below, this is not finding. AUTOEXP 50 60

Fix: F-41081r649575_fix

Include an “AUTOEXP” record in the “SECURITY CONFIG” file that is configured as follows: AUTOEXP 50 60

CA VM:Secure product PASSWORD user exit must be coded with the PWLIST option properly set.

IA-5 - Medium - CCI-000200 - V-237913 - SV-237913r649579_rule

RMF Control

IA-5

Severity

CCI

CCI-000200

Version

IBMZ-VM-000510

Vuln IDs

V-237913
V-78873

Rule IDs

SV-237913r649579_rule
SV-93579

Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user to consecutively reuse their password when that password has exceeded its defined lifetime, the end result is a password that is not changed as per policy requirements.

Checks: C-41123r649577_chk

If there is no CA VM:Secure Product PASSWORD user exit in use, this is a finding. Examine the CA VM:Secure product PASSWORD user exit for requirement that uses a “PWLIST” option that prohibits password reuse for five generations. If this code is missing, this is a finding.

Fix: F-41082r649578_fix

Engineer code in the CA VM:Secure Product PASSWORD user exit that uses a “PWLIST” that prohibits password reuse for five generations.

IBM zVM CA VM:Secure product PASSWORD user exit must be in use.

IA-5 - Medium - CCI-000192 - V-237914 - SV-237914r649582_rule

RMF Control

IA-5

Severity

CCI

CCI-000192

Version

IBMZ-VM-000520

Vuln IDs

V-237914
V-78875

Rule IDs

SV-237914r649582_rule
SV-93581

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 helps to determine strength and how long it takes to crack a password. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password. Satisfies: SRG-OS-000078-GPOS-00046, SRG-OS-000480-GPOS-00227, SRG-OS-000480-GPOS-00227, SRG-OS-000266-GPOS-00101, SRG-OS-000075-GPOS-00043, SRG-OS-000070-GPOS-00038, SRG-OS-000071-GPOS-00039, SRG-OS-000069-GPOS-00037, SRG-OS-000072-GPOS-00040

Checks: C-41124r649580_chk

If there is no CA VM:Secure PASSWORD user exit in use, this is a finding. Review the CA VM:Secure Password user exit. If there is no code that enforces a minimum 8-character password, this is a finding. If there is no code that prohibits the use of all numbers in the new password, this is a finding. If there is no code that prohibits the use of user name in the new password, this is a finding. If there is no code that prohibits the use of userID in the new password, this is a finding. If there is no code that prohibits the use of consecutive repeated characters, this is a finding. If there is no code requiring that at least one special character be used in the new password, this is a finding. If there is no code that enforces 24 hours/1 day as the minimum password lifetime, this is a finding. If there is no code that enforces a minimum that at least one lowercase character is used in the new password, this is a finding. If there is no code that enforces a minimum that at least one numeric character is used in the new password, this is a finding. If there is no code that enforces a minimum that at least one uppercase character is used in the new password, this is a finding. If there is no code that enforces change of at least 50% of the total number of characters when passwords are changed, this is a finding.

Fix: F-41083r649581_fix

Configure a CA VM:Secure PASSWORD user exit that enforces a minimum 8-character password length. Ensure that the following macros are updated with proper PASSWORD user exit: FORCEPWC VMXCHGPW MAINT USE00080

IBM z/VM must be configured to disable non-essential capabilities.

CM-7 - Medium - CCI-000381 - V-237915 - SV-237915r649585_rule

RMF Control

CM-7

Severity

CCI

CCI-000381

Version

IBMZ-VM-000560

Vuln IDs

V-237915
V-78877

Rule IDs

SV-237915r649585_rule
SV-93583

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 wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Examples of non-essential capabilities include, but are not limited to, games, software packages, tools, and demonstration software, not related to requirements or providing a wide array of functionality not required for every mission, but which cannot be disabled.

Checks: C-41125r649583_chk

Determine if the System administrator has a documented manual process to review and disable non-essential capabilities for z/VM. If there is no policy and process to review and disable non-essential capabilities, this is a finding. If capabilities identified in the policy are not disabled, this is a finding.

Fix: F-41084r649584_fix

Develop a policy for a procedure to review and disable non-essential capabilities for z/VM. Ensure that all identified non-essential capabilities are disabled.

CA VM:Secure product Config Delay LOG option must be set to 0.

CM-6 - Medium - CCI-000366 - V-237916 - SV-237916r649588_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-000590

Vuln IDs

V-237916
V-78879

Rule IDs

SV-237916r649588_rule
SV-93585

IBM z/VM 6.4.0 made changes to obscure whether a logon is invalid due to the user ID or due to the password. Both the logon prompting sequence and the message HCPLGA050E were changed. However, DELAYLOG causes a delay for a logon with an invalid password that it does not cause when the user ID is invalid. Thus, if you are using DELAYLOG with z/VM 6.4.0, you can inadvertently let someone trying to break into your system know that it is the password that is invalid.

Checks: C-41126r649586_chk

Display the CA VM:Secure product Config file. If the “DELAYLOG” record does not exist, this is not a finding. If the “DELAYLOG” record is set to "0”, this is not a finding.

Fix: F-41085r649587_fix

Configure DELAYLOG = 0 or delete the “DELAYLOG” configuration file record.

CA VM:Secure product NORULE record in the SECURITY CONFIG file must be configured to REJECT.

AC-3 - Medium - CCI-000213 - V-237917 - SV-237917r649591_rule

RMF Control

AC-3

Severity

CCI

CCI-000213

Version

IBMZ-VM-000600

Vuln IDs

V-237917
V-78881

Rule IDs

SV-237917r649591_rule
SV-93587

To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include: identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include: access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. Satisfies: SRG-OS-000080-GPOS-00048, SRG-OS-000480-GPOS-00228, SRG-OS-000480-GPOS-00229, SRG-OS-000104-GPOS-00051, SRG-OS-000121-GPOS-00062, SRG-OS-000370-GPOS-00155

Checks: C-41127r649589_chk

Examine the “SECURITY CONFIG” file. If a “NORULE” record exists and is set to “REJECT”, this is not a finding.

Fix: F-41086r649590_fix

Configure the “SECURITY CONFIG” file to include a “NORULE” record that is set to “REJECT”.

All IBM z/VM TCP/IP Ports must be restricted to ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

CM-7 - Medium - CCI-000382 - V-237918 - SV-237918r649594_rule

RMF Control

CM-7

Severity

CCI

CCI-000382

Version

IBMZ-VM-000630

Vuln IDs

V-237918
V-78883

Rule IDs

SV-237918r649594_rule
SV-93589

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 services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., VPN and IPS); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the operating system must support the organizational requirements, providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.

Checks: C-41128r649592_chk

For each TCP/IP server defined examine the TCP/IP Configuration Port Statements. Consult DISA Ports, Protocols, and Services Management (PPSM) Category Assurance Levels (CAL). Verify that the ports and protocols being used are not prohibited and are necessary for the operation of the application server and the hosted applications. If any of the ports or protocols is prohibited or not necessary for the application server operation, this is a finding.

Fix: F-41087r649593_fix

Configure the application server definition in TCP/IP configuration file to disable any ports or protocols that are prohibited by the PPSM CAL and vulnerability assessments.

The IBM z/VM Security Manager must provide a procedure to disable userIDs after 35 days of inactivity.

IA-4 - Medium - CCI-000795 - V-237919 - SV-237919r649597_rule

RMF Control

IA-4

Severity

CCI

CCI-000795

Version

IBMZ-VM-000650

Vuln IDs

V-237919
V-78885

Rule IDs

SV-237919r649597_rule
SV-93591

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 disable application identifiers after 35 days of inactivity.

Checks: C-41129r649595_chk

Examine the procedure for disabling user accounts. If the procedure performs the following steps, this is not a finding. - Monitors the time since last logon. - Checks all userIDs for inactivity more than 35 days. - If found, the ISSO must suspend an account, but not delete it until it is verified by the local ISSO that the user no longer requires access. - If verification is not received within 60 days, the account may be deleted.

Fix: F-41088r649596_fix

Develop a procedure that includes the following steps: - Monitors the time since last logon. - Checks all userIDs for inactivity more than 35 days. - If found, the ISSO must suspend an account, but not delete it until it is verified by the local ISSO that the user no longer requires access. - If verification is not received within 60 days, the account may be deleted.

The IBM z/VM TCP/IP VMSSL command operands must be configured properly.

IA-7 - High - CCI-000803 - V-237920 - SV-237920r649600_rule

RMF Control

IA-7

Severity

CCI

CCI-000803

Version

IBMZ-VM-000660

Vuln IDs

V-237920
V-78887

Rule IDs

SV-237920r649600_rule
SV-93593

VMSSL services are initiated using the VMSSL command defined in the DTCPARMS file. Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised.

Checks: C-41130r649598_chk

Determine and examine the “DTCPARMS” file for each SSL server pool. If the "VMSSL" command is not included in a :PARMS tag, this is a finding. If the “VMSSL” command is not configured as follows, this is a finding. FIPS (Operand FIPS is equivalent to setting MODE FIPS-140-2.) MODE FIPS-140-2 (Operand MODE FIPS-140-2 is equivalent to setting operand FIPS.) PROTOcol TLSV1_2

Fix: F-41089r649599_fix

Configure the SSL DTCPARMS file with a :PARMS tag that includes “VMSSL” command. Configure the “VMSSL” command to MODE FIPS-140-2, either by including the FIPS operand or by setting the “MODE” operand to FIPS-140-2. Include the PROTOcol operands for TLSV1_2.

The IBM z/VM TCP/IP ANONYMOU statement must not be coded in FTP configuration.

IA-8 - Medium - CCI-000804 - V-237921 - SV-237921r649603_rule

RMF Control

IA-8

Severity

CCI

CCI-000804

Version

IBMZ-VM-000680

Vuln IDs

V-237921
V-78889

Rule IDs

SV-237921r649603_rule
SV-93595

Operating systems utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules.

Checks: C-41131r649601_chk

If there is no FTP Server active, this is not applicable. Examine the “DTCPARMS” file for each active FTP server. If there is “:ANONYMOUS” or “:ANONYMOU” statement, this is a finding. Examine the “SRVRFTP” command. If “ANONYMOU” is coded, this is a finding.

Fix: F-41090r649602_fix

Ensure the “:ANONYMOUS” or “:ANONYMOU” statement is not coded in the “DTCPARMS” or “SRVRFTP” command.

CA VM:Secure product ADMIN GLOBALS command must be restricted to systems programming personnel.

SC-2 - Medium - CCI-001082 - V-237922 - SV-237922r649606_rule

RMF Control

SC-2

Severity

CCI

CCI-001082

Version

IBMZ-VM-000690

Vuln IDs

V-237922
V-78891

Rule IDs

SV-237922r649606_rule
SV-93597

Operating system management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access operating system management functionality capabilities increases the risk that non-privileged users may obtain elevated privileges. Operating system management functionality includes functions necessary to administer console, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, different TCP/UDP ports, virtualization techniques, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different security domain and with additional access controls.

Checks: C-41132r649604_chk

Examine the “AUTHORIZ” config file. If authorization to “ADMIN GLOBALS” is granted to “SYS Admin”, this is not a finding.

Fix: F-41091r649605_fix

Configure grant statements in the “AUTHORIZ” file using the “ADMIN GLOBALS” command that list Sys Admins only.

CA VM:Secure must have a security group for Security Administrators only.

SC-3 - Medium - CCI-001084 - V-237923 - SV-237923r649609_rule

RMF Control

SC-3

Severity

CCI

CCI-001084

Version

IBMZ-VM-000700

Vuln IDs

V-237923
V-78893

Rule IDs

SV-237923r649609_rule
SV-93599

An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Operating systems implement code separation (i.e., separation of security functions from non-security functions) in a number of ways, including through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that serve to protect the code on disk and address space protections that protect executing code. Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. Implementation may include isolation of memory space and libraries. Operating systems restrict access to security functions through the use of access control mechanisms and by implementing least privilege capabilities.

Checks: C-41133r649607_chk

Ask the Security Administrator for the defined groups that have authorization to perform security tasks, i.e., create and change rules for any userID in the Rules Facility. Examine the members (users) in each of these groups. If any user does not have the role of Security Administrator, this is a finding.

Fix: F-41092r649608_fix

Define a security group in the Rules Facility for Security Administrators only.

The IBM z/VM SYSTEM CONFIG file must be configured to clear TDISK on IPL.

SC-4 - Medium - CCI-001090 - V-237924 - SV-237924r649612_rule

RMF Control

SC-4

Severity

CCI

CCI-001090

Version

IBMZ-VM-000710

Vuln IDs

V-237924
V-78895

Rule IDs

SV-237924r649612_rule
SV-93601

Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the actions of prior users/roles (or the actions of processes acting on behalf of prior users/roles) from being available to any current users/roles (or current processes) that obtain access to shared system resources (e.g., registers, main memory, hard disks) after those resources have been released back to information systems. The control of information in shared resources is also commonly referred to as object reuse and residual information protection. This requirement generally applies to the design of an information technology product, but it can also apply to the configuration of particular information system components that are, or use, such products. This can be verified by acceptance/validation processes in DoD or other government agencies. There may be shared resources with configurable protections (e.g., files in storage) that may be assessed on specific information system components.

Checks: C-41134r649610_chk

Examine the SYSTEM CONFIG file. If the “Feature” statement specifies ENABLE CLEAR_TDISK, this is not a finding.

Fix: F-41093r649611_fix

Ensure that the following statement is in the SYSTEM CONFIG file: FEATURES ENABLE CLEAR_TDISK Further, before a minidisk is assigned to a user, the minidisk must be formatted to clear it of any residual data. CMS FORMAT, ICKDSF, or any other low-level formatting program that erases all of the data on the minidisk may be used.

The IBM z/VM TCP/IP FOREIGNIPCONLIMIT statement must be properly configured.

SC-5 - Medium - CCI-001095 - V-237925 - SV-237925r649615_rule

RMF Control

SC-5

Severity

CCI

CCI-001095

Version

IBMZ-VM-000720

Vuln IDs

V-237925
V-78897

Rule IDs

SV-237925r649615_rule
SV-93603

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. Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning. Use the FOREIGNIPCONLIMIT statement to define the maximum number of connections that a foreign IP address is allowed to have open at the same time. If this value would be exceeded, an SSTRESS denial-of-service attack is declared.

Checks: C-41135r649613_chk

Examine “TCP/IP” configuration file. If there is no “FOREIGNIPCONLIMIT” statement, this is a finding. If the “FOREIGNIPCONLIMIT” has a value of “0”, this is a finding.

Fix: F-41094r649614_fix

Configure the “FOREIGNIPCONLIMIT” statement with a value specifying the maximum number of connections that a foreign IP address is allowed to have open at the same time. The System Administrator should determine the proper value.

The IBM z/VM TCP/IP PERSISTCONNECTIONLIMIT statement must be properly configured.

SC-5 - Medium - CCI-001095 - V-237926 - SV-237926r649618_rule

RMF Control

SC-5

Severity

CCI

CCI-001095

Version

IBMZ-VM-000730

Vuln IDs

V-237926
V-78899

Rule IDs

SV-237926r649618_rule
SV-93605

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. Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning. The PERSISTCONNECTIONLIMIT statement defines the maximum number of connections in TCP persist state at any given time. When a new connection in persist state causes this limit to be exceeded, the oldest current connection in persist state is dropped and a ZeroWin denial-of-service attack is declared.

Checks: C-41136r649616_chk

Examine the “TCP/IP” configuration file. If there is no “PERSISTCONNECTIONLIMIT” statement, this is a finding.

Fix: F-41095r649617_fix

Configure the “PERSISTCONNECTIONLIMIT” statement with a value that is less than the “TCBPOOLSIZE”.

The IBM z/VM TCP/IP PENDINGCONNECTIONLIMIT statement must be properly configured.

SC-5 - Medium - CCI-001095 - V-237927 - SV-237927r649621_rule

RMF Control

SC-5

Severity

CCI

CCI-001095

Version

IBMZ-VM-000740

Vuln IDs

V-237927
V-78901

Rule IDs

SV-237927r649621_rule
SV-93607

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. Managing excess capacity ensures that sufficient capacity is available to counter flooding attacks. Employing increased capacity and service redundancy may reduce the susceptibility to some DoS attacks. Managing excess capacity may include, for example, establishing selected usage priorities, quotas, or partitioning. The PENDINGCONNECTIONLIMIT statement defines the maximum number of half-open connections that are allowed at any given time. When a new half-open connection causes this limit to be exceeded, a random current half-open connection is dropped and a SynFlood denial-of-service attack is declared.

Checks: C-41137r649619_chk

Examine the “TCP/IP” configuration file. If there is no “PENDINGCONNECTIONLIMIT” statement, this is a finding.

Fix: F-41096r649620_fix

Configure the “PENDINGCONNECTIONLIMIT” statement with a value that is less than the “TCBPOOLSIZE”.

IBM z/VM tapes must use Tape Encryption.

SC-28 - Medium - CCI-001199 - V-237928 - SV-237928r649624_rule

RMF Control

SC-28

Severity

CCI

CCI-001199

Version

IBMZ-VM-000750

Vuln IDs

V-237928
V-78903

Rule IDs

SV-237928r649624_rule
SV-93609

Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and tape drive, when used for backups) within an operating system. Guest operating systems, such as CMS, that are not capable of enabling the hardware encryption available with the 3592 Model E05 tape drive are able to use z/VM facilities that enable the encryption on behalf of the guest. Guest operating systems that do support tape encryption, such as z/OS with proper service, will be able to do so without interference from z/VM.

Checks: C-41138r649622_chk

Verify Tape Encryption is in use. For IBM drives issue the following command: Class B: QUERY TAPES DETAIL or Class G: QUERY VIRTUAL TAPES If resulting text includes “ACTIVE KEY LABELS”, this is not a finding. Regardless of the drive type if there is no encryption available, this is a finding.

Fix: F-41097r649623_fix

Consult CP Administration manual for procedures to set up IBM Device Encryption. For any other drive type consult manufacturer for encryption procedures.

The IBM z/VM TCP/IP must be configured to display the mandatory DoD Notice and Consent banner before granting access to the system.

AC-8 - Medium - CCI-001384 - V-237929 - SV-237929r649627_rule

RMF Control

AC-8

Severity

CCI

CCI-001384

Version

IBMZ-VM-000760

Vuln IDs

V-237929
V-78905

Rule IDs

SV-237929r649627_rule
SV-93611

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. 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. The banner must be formatted in accordance with applicable DoD policy. Use the following verbiage for operating systems that can accommodate banners of 1300 characters: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." Use the following verbiage for operating systems that have severe limitations on the number of characters that can be displayed in the banner: "I've read & consent to terms in IS user agreem't."

Checks: C-41139r649625_chk

Check the TELNET connection exit. If there is no TELNET connection exit, this is a finding. If the TELNET connection exit does not send a Notice and Consent message before access is granted, this is a finding.

Fix: F-41098r649626_fix

Configure the TELNET connection exit to display a Notice and Consent banner message before access is granted to TELNET.

The IBM z/VM JOURNALING statement must be coded on the configuration file.

AU-14 - Medium - CCI-001464 - V-237930 - SV-237930r649630_rule

RMF Control

AU-14

Severity

CCI

CCI-001464

Version

IBMZ-VM-000810

Vuln IDs

V-237930
V-78907

Rule IDs

SV-237930r649630_rule
SV-93613

If auditing is enabled late in the start-up process, the actions of some start-up processes may not be audited. Some audit systems also maintain state information only available if auditing is enabled before a given process is created.

Checks: C-41140r649628_chk

Examine the Product configuration file. If the “JOURNALING” statement does not specify “ON”, this is a finding.

Fix: F-41099r649629_fix

Configure the system configuration “JOURNALING” statement to “JOURNALING ON”.

CA VM:Secure product SECURITY CONFIG file must be restricted to appropriate personnel.

CM-6 - Medium - CCI-000366 - V-237931 - SV-237931r649633_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-000830

Vuln IDs

V-237931
V-78909

Rule IDs

SV-237931r649633_rule
SV-93615

Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order to make access decisions regarding the access to audit tools. 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. Satisfies: SRG-OS-000256-GPOS-00097, SRG-OS-000480-GPOS-00227

Checks: C-41141r649631_chk

Query the CA VM:Secure product rules. If there are product rules granting access to the disk on which the “SECURITY CONFIG” file resides for auditors, system administrators or security administrators only, this is not a finding.

Fix: F-41100r649632_fix

Create rules in the CA VM:Secure product Rules Facility that restricts access to the disk where the “SECURITY CONFIG” file resides to auditors, system administrators or security administrators only.

The IBM z/VM AUDT and Journal Mini Disks must be restricted to the appropriate system administrators.

AU-9 - Medium - CCI-001494 - V-237932 - SV-237932r649636_rule

RMF Control

AU-9

Severity

CCI

CCI-001494

Version

IBMZ-VM-000840

Vuln IDs

V-237932
V-78911

Rule IDs

SV-237932r649636_rule
SV-93617

Protecting audit information also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit information. Operating systems providing tools to interface with audit information will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user has in order to make access decisions regarding the modification of audit tools. 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. Satisfies: SRG-OS-000257-GPOS-00098, SRG-OS-000258-GPOS-00099

Checks: C-41142r649634_chk

Examine the CA VM:Secure rules. If there are Link rules for audit disk granted to anyone other than system administrators, security administrators, or system auditors, this is a finding.

Fix: F-41101r649635_fix

Create a CA VM:Secure rule that grants access to system administrators, security administrators, or system auditors only.

IBM z/VM must remove or disable emergency accounts after the crisis is resolved or 72 hours.

AC-2 - Medium - CCI-001682 - V-237933 - SV-237933r649639_rule

RMF Control

AC-2

Severity

CCI

CCI-001682

Version

IBMZ-VM-000860

Vuln IDs

V-237933
V-78913

Rule IDs

SV-237933r649639_rule
SV-93619

Emergency accounts are privileged accounts that are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If these accounts are automatically disabled, system maintenance during emergencies may not be possible, thus adversely affecting system availability. Emergency accounts are different from infrequently used accounts (i.e., local logon accounts used by the organization's system administrators when network or normal logon/access is not available). Infrequently used accounts are not subject to automatic termination dates. Emergency accounts are accounts created in response to crisis situations, usually for use by maintenance personnel. The automatic expiration or disabling time period may be extended as needed until the crisis is resolved; however, it must not be extended indefinitely. A permanent account should be established for privileged users who need long-term maintenance accounts. To address access requirements, many operating systems can be integrated with enterprise-level authentication/access mechanisms that meet or exceed access control policy requirements.

Checks: C-41143r649637_chk

Ask the system administrator (SA) for a documented process to remove or disable emergency accounts after a crisis has been resolved or 72 hours. If there is no documented process, this is a finding. If there are emergency accounts enabled check date/time of resolution of last crisis event. If date/time is greater than 72 hours, this is a finding.

Fix: F-41102r649638_fix

Develop a policy and process to remove or disable emergency accounts after a crisis has been resolved or 72 hours. Ensure that all emergency accounts are disabled after a crisis has been resolved or 72 hours.

The IBM z/VM must restrict link access to the disk on which system software resides.

CM-5 - Medium - CCI-001499 - V-237934 - SV-237934r649642_rule

RMF Control

CM-5

Severity

CCI

CCI-001499

Version

IBMZ-VM-000880

Vuln IDs

V-237934
V-78915

Rule IDs

SV-237934r649642_rule
SV-93621

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. This requirement applies to operating systems with software libraries that are accessible and configurable, as in the case of interpreted languages. Software libraries also include privileged programs which execute with escalated privileges. Only qualified and authorized individuals must be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.

Checks: C-41144r649640_chk

Examine the CA VM:Secure rules. If there are Link rules for system software disks granted to anyone other than system administrators, this is a finding.

Fix: F-41103r649641_fix

Create a CA VM:Secure rule that grants access for system software disks to system administrators only.

The IBM z/VM Privilege command class A and Class B must be properly assigned.

CM-11 - Medium - CCI-001812 - V-237935 - SV-237935r649645_rule

RMF Control

CM-11

Severity

CCI

CCI-001812

Version

IBMZ-VM-000900

Vuln IDs

V-237935
V-78917

Rule IDs

SV-237935r649645_rule
SV-93623

Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceeds the rights of a regular user. Operating system functionality will vary, and while users are not permitted to install unapproved software, there may be instances where the organization allows the user to install approved software packages, such as from an approved software repository. The operating system or software configuration management utility must enforce control of software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization.

Checks: C-41145r649643_chk

Examine CP Directory. If Privilege CLASS A or B is granted to anyone other than systems administrators or systems operators, this is a finding. Note: Restrict link to disk where system software resides.

Fix: F-41104r649644_fix

Configure the IBM z/VM to grant CP Privilege Class A or B to system administrators or system operators only.

CA VM:Secure AUTHORIZ CONFIG file must be properly configured.

CM-5 - Medium - CCI-001813 - V-237936 - SV-237936r649648_rule

RMF Control

CM-5

Severity

CCI

CCI-001813

Version

IBMZ-VM-000910

Vuln IDs

V-237936
V-78919

Rule IDs

SV-237936r649648_rule
SV-93625

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 can have significant effects on the overall security of the system. Accordingly, only qualified and authorized individuals should be allowed to obtain access to operating system components for the purposes of initiating changes, including upgrades and modifications. Logical access restrictions include, for example, controls that restrict access to workflow automation, media libraries, abstract layers (e.g., changes implemented into third-party interfaces rather than directly into information systems), and change windows (e.g., changes occur only during specified times, making unauthorized changes easy to discover).

Checks: C-41146r649646_chk

Examine “AUTHORIZ CONFIG” file. If Authorizations are granted as follows, this is not a finding. Grant the CA VM:Secure system administrator authorization to use all commands and menu selections. Grant directory managers authorization to use a particular command, group of commands, or menu selection. By carefully planning these authorizations, you can delegate many of the daily directory and disk space management tasks to the directory managers. Plan these authorizations carefully to cover all aspects of your site’s VM installation. Grant general users authorization to use those commands and menu selections that enable them to manage their own virtual machine. Users can then perform tasks such as maintaining their own system password and controlling access to their minidisks by others.

Fix: F-41105r649647_fix

Assure that the following authorizations are configured: Grant the CA VM:Secure system administrator authorization to use all commands and menu selections. Grant directory managers authorization to use a particular command, group of commands, or menu selection. By carefully planning these authorizations, you can delegate many of the daily directory and disk space management tasks to the directory managers. Plan these authorizations carefully to cover all aspects of your site’s VM installation. Grant general users authorization to use those commands and menu selections that enable them to manage their own virtual machine. Users can then perform tasks such as maintaining their own system password and controlling access to their minidisks by others. For example, for users in the Technical Support group, you may want to authorize them to use all selections on the “User Selection” menu.

The IBM z/VM journal minidisk space allocation must be large enough for one weeks worth of audit records.

AU-4 - Medium - CCI-001849 - V-237937 - SV-237937r649651_rule

RMF Control

AU-4

Severity

CCI

CCI-001849

Version

IBMZ-VM-000930

Vuln IDs

V-237937
V-78921

Rule IDs

SV-237937r649651_rule
SV-93627

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.

Checks: C-41147r649649_chk

Examine the “MDISK” statement for journaling. If the space allocations are not large enough for one weeks’ worth of audit records, this is a finding.

Fix: F-41106r649650_fix

Monitor journal minidisks for required space allocation for one week's worth of data. The system administrator will determine the required space allocation. Assure space allocation is large enough for one week of audit records.

CA VM:Secure product audit records must offload audit records to a different system or media.

AU-4 - Medium - CCI-001851 - V-237938 - SV-237938r649654_rule

RMF Control

AU-4

Severity

CCI

CCI-001851

Version

IBMZ-VM-000940

Vuln IDs

V-237938
V-78923

Rule IDs

SV-237938r649654_rule
SV-93629

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.

Checks: C-41148r649652_chk

If there is no documented process for audit offload, this is a finding. Examine the documented user process for audit record offload. If the procedure does not offload to a different system or media, this is a finding.

Fix: F-41107r649653_fix

Develop a user written procedure to offload audit records to a different system or media.

CA VM:Secure product audit records must be offloaded on a weekly basis.

AU-4 - Medium - CCI-001851 - V-237939 - SV-237939r649657_rule

RMF Control

AU-4

Severity

CCI

CCI-001851

Version

IBMZ-VM-000950

Vuln IDs

V-237939
V-78925

Rule IDs

SV-237939r649657_rule
SV-93631

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.

Checks: C-41149r649655_chk

Check audit offload procedure. If it can be determined that the audit records are being offloaded on a weekly basis, this is not a finding.

Fix: F-41108r649656_fix

Develop procedures that offload Audit minidisk on a weekly basis.

The IBM z/VM Portmapper server virtual machine userID must be included in the AUTOLOG statement of the TCP/IP server configuration file.

IA-3 - Medium - CCI-001967 - V-237940 - SV-237940r649660_rule

RMF Control

IA-3

Severity

CCI

CCI-001967

Version

IBMZ-VM-000960

Vuln IDs

V-237940
V-78927

Rule IDs

SV-237940r649660_rule
SV-93633

Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. Bidirectional authentication solutions include, but are not limited to, IEEE 802.1x and Extensible Authentication Protocol [EAP], RADIUS server with EAP-Transport Layer Security [TLS] authentication, Kerberos, and SSL mutual authentication. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area network, wide area network, or the Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply this requirement to those limited number (and type) of devices that truly need to support this capability.

Checks: C-41150r649658_chk

Examine the TCP/IP configuration for “AUTOLOG”. If the userID for auto logger is not in the “AUTOLOG” statement of the TCP/IP server configuration file, this is a finding.

Fix: F-41109r649659_fix

Include the Portmapper server virtual machine userID in the “AUTOLOG” statement of the TCP/IP server configuration file. The Portmapper server is then automatically started when TCP/IP is initialized. The IBM default userID for this server is PORTMAP, but review installation to assure proper ID is included.

CA VM:Secure product MANAGE command must be restricted to system administrators.

AC-3 - Medium - CCI-002165 - V-237941 - SV-237941r649663_rule

RMF Control

AC-3

Severity

CCI

CCI-002165

Version

IBMZ-VM-000980

Vuln IDs

V-237941
V-78929

Rule IDs

SV-237941r649663_rule
SV-93635

Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled file permissions. When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. The policy is bounded by the information system boundary. Once the information is passed outside the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.

Checks: C-41151r649661_chk

Examine “AUTHORIZ CONFIG” file. If the “MANAGE” command is only granted to system administrators, this is not a finding.

Fix: F-41110r649662_fix

Include the “GRANT” statement for the “MANAGE” command to restrict to system administrators only.

The CA VM:Secure LOGONBY command must be restricted to system administrators.

AC-6 - Medium - CCI-002233 - V-237942 - SV-237942r649666_rule

RMF Control

AC-6

Severity

CCI

CCI-002233

Version

IBMZ-VM-000990

Vuln IDs

V-237942
V-78931

Rule IDs

SV-237942r649666_rule
SV-93637

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. The LOGONBY statement designates up to eight user IDs that can use their own passwords to log on to and use the virtual machine.

Checks: C-41152r649664_chk

Examine the CA VM:Secure Rules facility for “LOGONBY” rules. If the “LOGONBY” rules specifies users that are not system administrators, this is a finding.

Fix: F-41111r649665_fix

Assure that any “LOGONBY” rules in the CA VM:Secure Rules Facility only specifies users who are system administrators.

The IBM z/VM CP Privilege Class A, B, and D must be restricted to appropriate system operators.

AC-6 - Medium - CCI-002235 - V-237943 - SV-237943r649669_rule

RMF Control

AC-6

Severity

CCI

CCI-002235

Version

IBMZ-VM-001010

Vuln IDs

V-237943
V-78933

Rule IDs

SV-237943r649669_rule
SV-93639

Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. 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.

Checks: C-41153r649667_chk

Examine user directory definitions to determine CP Privilege class. If CP Privilege Class A, B, or D is assigned to non-privilege users, this is a finding.

Fix: F-41112r649668_fix

Ensure that non-privilege users are not assigned CP Privilege Class A, B, or D.

The IBM z/VM JOURNALING statement must be properly configured.

AC-7 - Medium - CCI-002238 - V-237944 - SV-237944r649672_rule

RMF Control

AC-7

Severity

CCI

CCI-002238

Version

IBMZ-VM-001020

Vuln IDs

V-237944
V-78935

Rule IDs

SV-237944r649672_rule
SV-93641

By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.

Checks: C-41154r649670_chk

View system config “JOURNALING” statement. If the “JOURNALING” statement “LOGON” operand is configured as below, this is not a finding. Logon, Account after 3 attempts, See IBMZ-VM-000040 for LOCKOUT setting. Link, Account after 3 attempts, Disable after 3 attempts

Fix: F-41113r649671_fix

Configure the system config “JOURNALING” statement to include the following: Logon, Account after 3 attempts, See IBMZ-VM-000040 for LOCKOUT setting. Link, Account after 3 attempts, Disable after 3 attempts

The IBM z/VM TCP/IP SECUREDATA option for FTP must be set to REQUIRED.

SC-8 - Medium - CCI-002420 - V-237945 - SV-237945r649675_rule

RMF Control

SC-8

Severity

CCI

CCI-002420

Version

IBMZ-VM-001040

Vuln IDs

V-237945
V-78937

Rule IDs

SV-237945r649675_rule
SV-93643

Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. Ensuring the confidentiality of transmitted information requires the operating system to take measures in preparing information for transmission. This can be accomplished via access control and encryption. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When transmitting data, operating systems need to support transmission protection mechanisms such as TLS, SSL VPNs, or IPsec. The SECUREDATA statement specifies the FTP server-wide minimum security level for data connections. Satisfies: SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190

Checks: C-41155r649673_chk

Examine the FTP Server configuration file. If there is no “SECUREDATA” statement, this is a finding. If the “SECUREDATA” statement specifies “REQUIRED”, this is not a finding. Note: If there is no "SECUREDATA" or the "SECUREDATA" specifies "ALLOWED" but there is a documented implementation plan with a definite completion date for setting "SECUREDATA" to "REQUIRED" on file with the ISSM, this can be downgraded to a CAT III.

Fix: F-41114r649674_fix

Configure the “SECUREDATA” statement in the FTP server configuration file to specify “REQUIRED”. Note: Care should be taken before implementing this requirement in a production environment. Develop a documented plan of action that has a definite completion date. File the plan with the ISSM.

IBM z/VM TCP/IP config file INTERNALCLIENTPARMS statement must be properly configured.

AC-17 - Medium - CCI-002314 - V-237946 - SV-237946r649678_rule

RMF Control

AC-17

Severity

CCI

CCI-002314

Version

IBMZ-VM-001060

Vuln IDs

V-237946
V-78939

Rule IDs

SV-237946r649678_rule
SV-93645

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 an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Operating system functionality (e.g., RDP) must be capable of taking enforcement action if the audit reveals unauthorized activity. Automated control of remote access sessions allows organizations to ensure ongoing compliance with remote access policies by enforcing connection rules of remote access applications on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets). The INTERNALCLIENTPARMS statement is used to configure the Telnet server, an internal client of the TCPIP virtual machine.

Checks: C-41156r649676_chk

Examine the TCP/IP config file “INTERNALCLIENTPARMS” statement. If the following “INTERNALCLIENTPARMS” sub statement are included, this is not a finding. PORT Num not 20 or 21 SECURECONNECTION REQUIRED CLIENTCERTCHECK FULL

Fix: F-41115r649677_fix

Configure the TCP/IP config “INTERNALCLIENTPARM” statement to include the following: PORTNUM <secure FTP PORT Number> SECURECONNECTION REQUIRED CLIENTCERTCHECK FULL

All IBM z/VM TCP/IP servers must be configured for SSL/TLS connection.

SC-8 - Medium - CCI-002420 - V-237947 - SV-237947r649681_rule

RMF Control

SC-8

Severity

CCI

CCI-002420

Version

IBMZ-VM-001070

Vuln IDs

V-237947
V-78941

Rule IDs

SV-237947r649681_rule
SV-93647

Checks: C-41157r649679_chk

Determine SSL/TLS capability. Examine the TCP/IP config file. If the “SSLSERVERID” statement identifies at least one userID for SSL server, this is not a finding.

Fix: F-41116r649680_fix

Configure the “SSLSERVERID” statement to force auto logging of an SSL server before all other servers in the “AUTOLOG” list.

The IBM z/VM TCP/IP SECURETELNETCLIENT option for telnet must be set to YES.

SC-8 - Medium - CCI-002422 - V-237948 - SV-237948r649684_rule

RMF Control

SC-8

Severity

CCI

CCI-002422

Version

IBMZ-VM-001090

Vuln IDs

V-237948
V-78943

Rule IDs

SV-237948r649684_rule
SV-93649

Checks: C-41158r649682_chk

Examine the TCP/IP DATA file. If “SECURETELNETCLIENT” option is set to “YES”, this is not a finding.

Fix: F-41117r649683_fix

Configure the TCP/IP DATA file “SECURETELNETCLIENT” option to “YES”.

The IBM z/VM Privilege Classes C and E must be restricted to appropriate system administrators.

AC-6 - Medium - CCI-002235 - V-237954 - SV-237954r649702_rule

RMF Control

AC-6

Severity

CCI

CCI-002235

Version

IBMZ-VM-001190

Vuln IDs

V-237954
V-78955

Rule IDs

SV-237954r649702_rule
SV-93661

Checks: C-41164r649700_chk

Examine user directory definitions to determine privilege class. If the CP privilege Class C is assigned to system programmers only, this is not a finding. If the CP privilege Class E is assigned to system analyst only, this is not a finding.

Fix: F-41123r649701_fix

Configure the CP Privilege Class. Assign CP Privilege Classes, C and E, to system programmers and/or system analysts only.

The IBM z/VM Privilege Class F must be restricted to service representatives and system administrators only.

AC-6 - Medium - CCI-002235 - V-237955 - SV-237955r649705_rule

RMF Control

AC-6

Severity

CCI

CCI-002235

Version

IBMZ-VM-001200

Vuln IDs

V-237955
V-78957

Rule IDs

SV-237955r649705_rule
SV-93663

Checks: C-41165r649703_chk

Examine user directory definitions to determine Privilege Class. If CP Privilege Class F is assigned to anyone other than a service representative or system administrator, this is a finding.

Fix: F-41124r649704_fix

Configure CP Privilege Class F to service representatives and system administrators only.

The IBM z/VM ANY Privilege Class must not be listed for privilege commands.

AC-6 - Medium - CCI-002235 - V-237956 - SV-237956r649708_rule

RMF Control

AC-6

Severity

CCI

CCI-002235

Version

IBMZ-VM-001210

Vuln IDs

V-237956
V-78959

Rule IDs

SV-237956r649708_rule
SV-93665

Checks: C-41166r649706_chk

Examine defined-privileged commands. If any of the defined-privileged commands are defined with Privilege Class “ANY”, this is a finding.

Fix: F-41125r649707_fix

Review the defined-privileged commands. Assure that CP privileged commands are not defined with a Privilege Class of “ANY”.

CA VM:Secure product VMXRPI configuration file must be restricted to authorized personnel.

CM-6 - Medium - CCI-000366 - V-237957 - SV-237957r649711_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001220

Vuln IDs

V-237957
V-78961

Rule IDs

SV-237957r649711_rule
SV-93667

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, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. The VMXRPI CONFIG file contains records that determine the activity that can occur when the Rules Facility is not available, and provides the configuration information for the Rules Facility.

Checks: C-41167r649709_chk

Query the CA VM:Secure rules. If there are product rules granting access to the disk on which the “VMXRPI” configuration file resides for system administrators only, this is not a finding.

Fix: F-41126r649710_fix

Create rules in the CA VM:Secure product Rules Facility that restricts access to the disk where the “VMXRPI” configuration file resides to system administrators only.

CA VM:Secure product DASD CONFIG file must be restricted to appropriate personnel.

CM-6 - Medium - CCI-000366 - V-237958 - SV-237958r649714_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001230

Vuln IDs

V-237958
V-78963

Rule IDs

SV-237958r649714_rule
SV-93669

Checks: C-41168r649712_chk

Query the CA VM:Secure product rules. If there are product rules granting access to the disk on which the “DASD CONFIG” file resides for system administrators or DASD administrators only, this is not a finding.

Fix: F-41127r649713_fix

Create rules in the CA VM:Secure product Rules Facility that restricts access to the disk where the “DASD CONFIG” file resides to system administrators or DASD administrators only.

CA VM:Secure product AUTHORIZ CONFIG file must be restricted to appropriate personnel.

CM-6 - Medium - CCI-000366 - V-237959 - SV-237959r649717_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001240

Vuln IDs

V-237959
V-78965

Rule IDs

SV-237959r649717_rule
SV-93671

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, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. The AUTHORIZ CONFIG file is used to tailor user authorizations for CA VM:Secure commands.

Checks: C-41169r649715_chk

Query the CA VM:Secure product rules. If there are product rules granting access to the disk on which the “AUTHORIZ CONFIG” file resides for system administrators or security administrators only, this is not a finding.

Fix: F-41128r649716_fix

Create rules in the CA VM:Secure product Rules Facility that restricts access to the disk where the “AUTHORIZ CONFIG” file resides to system administrators or security administrators only.

CA VM:Secure product CONFIG file must be restricted to appropriate personnel.

CM-6 - Medium - CCI-000366 - V-237960 - SV-237960r649720_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001250

Vuln IDs

V-237960
V-78967

Rule IDs

SV-237960r649720_rule
SV-93673

Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections.

Checks: C-41170r649718_chk

Query the CA VM:Secure Product rules. If there are product rules granting access to the disk on which the product “CONFIG” file resides for system administrators only, this is not a finding.

Fix: F-41129r649719_fix

Create rules in the CA VM:Secure product Rules Facility that restricts access to the disk where the product “CONFIG” file resides to system administrators only.

CA VM:Secure Product SFS configuration file must be restricted to appropriate personnel.

CM-6 - Medium - CCI-000366 - V-237961 - SV-237961r649723_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001270

Vuln IDs

V-237961
V-78969

Rule IDs

SV-237961r649723_rule
SV-93675

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, software, or firmware components of the system that affect the security posture and/or functionality of the system. Security-related parameters are those parameters impacting the security state of the system, including the parameters required to satisfy other security control requirements. Security-related parameters include, for example: registry settings; account, file, directory permission settings; and settings for functions, ports, protocols, services, and remote connections. The SFS Configuration file is used to control the addition/deletion of file pools and user storage groups.

Checks: C-41171r649721_chk

Query the CA VM:Secure product rules. If there are product rules granting access to the disk on which the “SFS” configuration file resides for system administrators or DASD administrators only, this is not a finding.

Fix: F-41130r649722_fix

Create rules in the CA VM:Secure product Rules Facility that restricts access to the disk where the “SFS” configuration file resides to system administrators or DASD administrators only.

CA VM:Secure product Rules Facility must be restricted to appropriate personnel.

CM-6 - Medium - CCI-000366 - V-237962 - SV-237962r649726_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001280

Vuln IDs

V-237962
V-78971

Rule IDs

SV-237962r649726_rule
SV-93677

Checks: C-41172r649724_chk

Issue Command: VMSECURE CONFIG AUTHORIZ Inspect the "GRANT" statements. If there are statements that grant the authority to create system rules or rules that apply to other users is only granted to appropriate personnel, this is not a finding.

Fix: F-41131r649725_fix

Ensure the product Rules Facility is installed. Ensure that authority to create system rules or rules that apply to other users is only granted to appropriate personnel.

IBM z/VM must employ a Session manager.

CM-6 - Medium - CCI-000366 - V-237963 - SV-237963r649729_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002330

Vuln IDs

V-237963
V-78973

Rule IDs

SV-237963r649729_rule
SV-93679

A session manager controls the semi-permanent interactive information interchange, also known as a dialogue, between a user and z/VM. Without the use of a session manager these semi-permanent interchanges can be open to compromise and attacks.

Checks: C-41173r649727_chk

Examine running systems. If access is gained to the z/VM system without going through a session manager, this is a finding.

Fix: F-41132r649728_fix

Ensure that a session manager is in use with the system.

The IBM z/VM System administrator must develop a notification routine for account management.

CM-6 - Medium - CCI-000366 - V-237964 - SV-237964r649732_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002340

Vuln IDs

V-237964
V-78975

Rule IDs

SV-237964r649732_rule
SV-93681

Information system accounts are utilized for identifying individual users or for identifying the operating system processes themselves. In order to detect and respond to events affecting user accessibility and system processing, operating systems must not only audit vital account actions but, as required, notify the appropriate individuals so they can investigate the event. Such a capability greatly reduces the risk that operating system accessibility will be negatively affected for extended periods of time and provides logging that can be used for forensic purposes.

Checks: C-41174r649730_chk

Ask the system administrator (SA) for documented procedures and routines for account management. If there is no procedure or the procedure is not documented and filed with the ISSO, this is a finding.

Fix: F-41133r649731_fix

Develop processes, routines, and/or scripts for the notification of account management.

The IBM z/VM system administrator must develop routines and processes for the proper configuration and maintenance of Software.

CM-6 - Medium - CCI-000366 - V-237965 - SV-237965r649735_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002350

Vuln IDs

V-237965
V-78977

Rule IDs

SV-237965r649735_rule
SV-93683

Proper configuration management procedures for information systems provide for the proper configuration and maintenance in accordance with local policies restrictions and/or rules. Failure to properly configure and maintain system software and applications on the information system could result in a weakened security posture.

Checks: C-41175r649733_chk

Ask the system administrator (SA) for documented procedures and routines for proper configuration management of software. If there are no procedures or the procedures are not documented and on file with the ISSO, this is a finding.

Fix: F-41134r649734_fix

Develop a procedure for proper configuration of software components. Include proper maintenance procedures.

IBM z/VM must be protected by an external firewall that has a deny-all, allow-by-exception policy.

CM-6 - Medium - CCI-000366 - V-237966 - SV-237966r649738_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002360

Vuln IDs

V-237966
V-78979

Rule IDs

SV-237966r649738_rule
SV-93685

Firewalls protect computers from network attacks by blocking or limiting access to open network ports. Firewalls provide monitoring and control of communications at the external boundary of an information system to prevent and detect malicious and other unauthorized communications.

Checks: C-41176r649736_chk

Ask the system administrator for a network system plan. If there is no firewall defined for the IBM z/VM system, this is a finding. If the firewall does not have a deny-all, allow-by-exception policy, this is a finding.

Fix: F-41135r649737_fix

Ensure that the network has a firewall installed that provides a deny-all, allow-by-exception protection for the IBM z/VM system.

The IBM z/VM System administrator must develop routines and processes for notification in the event of audit failure.

CM-6 - Medium - CCI-000366 - V-237967 - SV-237967r649741_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002370

Vuln IDs

V-237967
V-78981

Rule IDs

SV-237967r649741_rule
SV-93687

Audit processing failures include, for example, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Without proper notification vital audit records may be lost.

Checks: C-41177r649739_chk

Ask the system administrator (SA) for documented routines and procures for notification in the event of audit failure. If there are no routines or procedures or they are not documented and filed with the ISSO, this is a finding.

Fix: F-41136r649740_fix

Develop a procedure for notification in the event of audit failure.

The IBM z/VM system administrator must develop procedures maintaining information system operation in the event of anomalies.

CM-6 - Medium - CCI-000366 - V-237968 - SV-237968r649744_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002380

Vuln IDs

V-237968
V-78983

Rule IDs

SV-237968r649744_rule
SV-93689

If anomalies are not acted upon, security functions may fail to secure the system.

Checks: C-41178r649742_chk

Ask the system administrator for a procedure to notify appropriate personnel in the event of system anomalies or failure. If there is no procedure for notification and resolution or they are not documented and on file with the ISSO, this is a finding.

Fix: F-41137r649743_fix

Develop a procedure for the notification and resolution of operation information system operation anomalies. Assure that procedures are documented and filed with the ISSO/ISSM.

IBM z/VM system administrator must develop procedures to manually control temporary, interactive, and emergency accounts.

CM-6 - Medium - CCI-000366 - V-237969 - SV-237969r649747_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002390

Vuln IDs

V-237969
V-78985

Rule IDs

SV-237969r649747_rule
SV-93691

Proper handling of temporary, inactive, and emergency accounts require automatic notification and action rather than at the convenience of the systems administrator. However in the absence of automated process manual procedures must be in place to assure that possible sensitive accounts are not compromised.

Checks: C-41179r649745_chk

Ask the system administrator (SA) for documented manual procedures to handle temporary, inactive, and emergency accounts. If there are no procedures or they are not documented and filed with the ISSM/ISSO, this is a finding.

Fix: F-41138r649746_fix

Develop a manual procedure to handle temporary, inactive, and emergency accounts in accordance with appropriate policies. Ensure that the procedures are documented and filed with ISSM/ISSO.

IBM z/VM must have access to an audit reduction tool that allows for central data review and analysis.

CM-6 - Medium - CCI-000366 - V-237970 - SV-237970r649750_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002400

Vuln IDs

V-237970
V-78987

Rule IDs

SV-237970r649750_rule
SV-93693

Audit reduction is a process that manipulates collected audit information and organizes such information in a summary format that is more meaningful to analysts. Audit reduction and report generation capabilities do not always emanate from the same information system or from the same organizational entities conducting auditing activities. Audit reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. Audit records may at times be voluminous. Without a reduction tool crucial information may be overlooked.

Checks: C-41180r649748_chk

Ask the system administrator if there is an audit reduction tool available for use with IBM z/VM. Determine if a process is established to route audit records to the tool. If there is no audit tool available, this is a finding. If a procedure for routing audit records to the tool is not documented and on file with the ISSM/ISSO, this is a finding.

Fix: F-41139r649749_fix

Develop a process for routing audit records to an audit reduction tool. Document the process and file with the ISSM/ISSO.

The IBM z/VM system administrator must develop and perform a procedure to validate the correct operation of security functions.

CM-6 - Medium - CCI-000366 - V-237971 - SV-237971r649753_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002410

Vuln IDs

V-237971
V-78989

Rule IDs

SV-237971r649753_rule
SV-93695

Without verification of the security functions, security functions may not operate correctly and the failure may go unnoticed. 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 functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. This requirement applies to operating systems performing security function verification/testing and/or systems and environments that require this functionality.

Checks: C-41181r649751_chk

Ask the system administrator (SA) if there is a documented procedure for validation of security functions on file with the ISSM/ISSO. If there is none, this is a finding. Ask for evidence that the procedures are performed. If there is no evidentiary proof, this is a finding.

Fix: F-41140r649752_fix

Develop a procedure that validates all security functions. Develop a log depicting date and time of validation signed by action official.

IBM z/VM must employ Clock synchronization software.

CM-6 - Medium - CCI-000366 - V-237972 - SV-237972r649756_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002420

Vuln IDs

V-237972
V-78991

Rule IDs

SV-237972r649756_rule
SV-93697

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 information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints).

Checks: C-41182r649754_chk

Determine if Clock synchronization software is use. If there is no Clock synchronization software in use, this is a finding. Determine if configuration allows for the synchronizing internal Clock to authoritative source. If software is improperly configured, this is a finding.

Fix: F-41141r649755_fix

Configure Clock synchronizing software to compare internal clock to authoritative source at least every 24 hours and when time difference is greater than one second.

The IBM z/VM systems requiring data at rest must employ IBMs DS8000 for full disk encryption.

CM-6 - Medium - CCI-000366 - V-237973 - SV-237973r649759_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-002430

Vuln IDs

V-237973
V-78993

Rule IDs

SV-237973r649759_rule
SV-93699

Operating systems handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields).

Checks: C-41183r649757_chk

Determine if IBM's DS8000 Disks are in use. If they are not in use for systems that require "data at rest", this is a finding.

Fix: F-41142r649758_fix

Employ IBM's DS8000 hardware to ensure full disk encryption.

The IBM z/VM TCP/IP NSLOOKUP statement for UFT servers must be properly configured.

CM-6 - Medium - CCI-000366 - V-245530 - SV-245530r755020_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001110

Vuln IDs

V-245530
V-78945

Rule IDs

SV-245530r755020_rule
SV-93651

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 DoS. Data origin authentication must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to enable clients to verify the authenticity of response data. This is not applicable if DNSSEC is not implemented on the local network.

Checks: C-48805r755018_chk

Examine the “UFTD CONFIG” file. If “NSLOOKUP” statement is “YES”, this is not a finding.

Fix: F-48761r755019_fix

Configure the “NSLOOKUP” statement in the “UFTD CONFIG” file to “YES”.

The IBM z/VM TCP/IP DOMAINLOOKUP statement must be properly configured.

CM-6 - Medium - CCI-000366 - V-245531 - SV-245531r755023_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001120

Vuln IDs

V-245531
V-78947

Rule IDs

SV-245531r755023_rule
SV-93653

Checks: C-48806r755021_chk

Examine the “TCPIP DATA” configuration file. If “DOMAINLOOKUP” statement is configured to “DNS”, this is not a finding.

Fix: F-48762r755022_fix

Configure the “DOMAINLOOKUP” statement to “DNS”.

The IBM z/VM TCP/IP NSINTERADDR statement must be present in the TCPIP DATA configuration.

CM-6 - Medium - CCI-000366 - V-245532 - SV-245532r755026_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001130

Vuln IDs

V-245532
V-78949

Rule IDs

SV-245532r755026_rule
SV-93655

Checks: C-48807r755024_chk

Examine the “TCPIP DATA” configuration file. If there is no “NSINTERADDR” statement in the “TCPIP DATA” configuration file, this is a finding.

Fix: F-48763r755025_fix

Configure the “NSINTERADDR” statement in the “TCPIP DATA” configuration file to an appropriate address.

The IBM z/VM CHECKSUM statement must be included in the TCP/IP configuration file.

CM-6 - Medium - CCI-000366 - V-245533 - SV-245533r755029_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001140

Vuln IDs

V-245533
V-78951

Rule IDs

SV-245533r755029_rule
SV-93657

If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data integrity verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. The CHECKSUM statement is a TCP/IP configuration file statement that instructs the TCPIP virtual machine to reenable TCP checksum testing on incoming messages.

Checks: C-48808r755027_chk

Examine the “TCP/IP” configuration file. If there is no “CHECKSUM” statement in the “TCP/IP” configuration file, this is a finding.

Fix: F-48764r755028_fix

Configure the “TCP/IP” configuration file to include a “CHECKSUM” statement.

The IBM z/VM DOMAINSEARCH statement in the TCPIP DATA file must be configured with proper domain names for name resolution.

CM-6 - Medium - CCI-000366 - V-245534 - SV-245534r755032_rule

RMF Control

CM-6

Severity

CCI

CCI-000366

Version

IBMZ-VM-001150

Vuln IDs

V-245534
V-78953

Rule IDs

SV-245534r755032_rule
SV-93659

If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data origin authentication verification must be performed to thwart these types of attacks. Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. This is not applicable if DNSSEC is not implemented on the local network.

Checks: C-48809r755030_chk

Examine the “TCPIP DATA” file. The domain specified for the “DOMAINORIGIN” statement is also used for host name resolution, as if it appeared in a “DOMAINSEARCH” statement. If there is no "DOMAINORIGIN" or “DOMAINSEARCH” statement, this is a finding. If the “DOMAINSEARCH” statement does not specify a proper domain, this is a finding. If the “DOMAINORIGIN” statement does not specify a proper domain, this is a finding.

Fix: F-48765r755031_fix

Configure any statement in the “TCPIP DATA” file used during host name resolution such as “DOMAINSEARCH” statement or the "DOMAINORIGIN" statement with a proper domain name.

Added rules 77

Removed rules 77

Checks: C-41107r649529_chk

Fix: F-41066r649530_fix

Generate Mitigation Statement:

Checks: C-41108r649532_chk

Fix: F-41067r649533_fix

Generate Mitigation Statement:

Checks: C-41109r649535_chk

Fix: F-41068r649536_fix

Generate Mitigation Statement:

Checks: C-41110r649538_chk

Fix: F-41069r649539_fix

Generate Mitigation Statement:

Checks: C-41111r649541_chk

Fix: F-41070r649542_fix

Generate Mitigation Statement:

Checks: C-41112r649544_chk

Fix: F-41071r649545_fix

Generate Mitigation Statement:

Checks: C-41113r649547_chk

Fix: F-41072r649548_fix

Generate Mitigation Statement:

Checks: C-41114r649550_chk

Fix: F-41073r649551_fix

Generate Mitigation Statement:

Checks: C-41115r649553_chk

Fix: F-41074r649554_fix

Generate Mitigation Statement:

Checks: C-41116r649556_chk

Fix: F-41075r649557_fix

Generate Mitigation Statement:

Checks: C-41117r649559_chk

Fix: F-41076r649560_fix

Generate Mitigation Statement:

Checks: C-41118r649562_chk

Fix: F-41077r649563_fix

Generate Mitigation Statement:

Checks: C-41119r649565_chk

Fix: F-41078r649566_fix

Generate Mitigation Statement:

Checks: C-41120r649568_chk

Fix: F-41079r649569_fix

Generate Mitigation Statement:

Checks: C-41121r649571_chk

Fix: F-41080r649572_fix

Generate Mitigation Statement:

Checks: C-41122r649574_chk

Fix: F-41081r649575_fix

Generate Mitigation Statement:

Checks: C-41123r649577_chk

Fix: F-41082r649578_fix

Generate Mitigation Statement:

Checks: C-41124r649580_chk

Fix: F-41083r649581_fix

Generate Mitigation Statement:

Checks: C-41125r649583_chk

Fix: F-41084r649584_fix

Generate Mitigation Statement:

Checks: C-41126r649586_chk

Fix: F-41085r649587_fix

Generate Mitigation Statement:

Checks: C-41127r649589_chk

Fix: F-41086r649590_fix

Generate Mitigation Statement:

Checks: C-41128r649592_chk

Fix: F-41087r649593_fix

Generate Mitigation Statement:

Checks: C-41129r649595_chk

Fix: F-41088r649596_fix

Generate Mitigation Statement:

Checks: C-41130r649598_chk

Fix: F-41089r649599_fix

Generate Mitigation Statement:

Checks: C-41131r649601_chk

Fix: F-41090r649602_fix

Generate Mitigation Statement:

Checks: C-41132r649604_chk

Fix: F-41091r649605_fix

Generate Mitigation Statement: