Mainframe Product Security Requirements Guide

This Security Requirements 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 e-mail to the following address: [email protected]

Details

Version / Release: V1R3

Published: 2019-10-08

Updated At: 2019-11-11 10:47:41

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter


Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-82291r1_rule SRG-APP-000001-MFP-000001 CCI-000054 MEDIUM The Mainframe Product must limit the number of concurrent sessions to three for all accounts and/or account types. Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement may
    SV-82599r1_rule SRG-APP-000002-MFP-000002 CCI-000060 MEDIUM The Mainframe Product must conceal, via the session lock, information previously visible on the display with a publicly viewable image. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not log out because of the temporary nature of the absence. The session lock is implemente
    SV-82601r1_rule SRG-APP-000003-MFP-000003 CCI-000057 MEDIUM The Mainframe Product must initiate a session lock after a 15-minute period of inactivity. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not log out because of the temporary nature of the absence. Rather than relying on the user
    SV-82603r1_rule SRG-APP-000004-MFP-000004 CCI-000058 MEDIUM The Mainframe Product must provide the capability for users to directly initiate a session lock. A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not want to log out because of the temporary nature of the absence. The session lock is implemented
    SV-82605r1_rule SRG-APP-000005-MFP-000005 CCI-000056 MEDIUM The Mainframe Product must retain the session lock until the user reestablishes access using established identification and authentication procedures. A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system, but does not want to log out because of the temporary nature of the absence. The session lock is implemented
    SV-82607r1_rule SRG-APP-000295-MFP-000006 CCI-002361 MEDIUM The Mainframe Product must automatically terminate a user session after conditions, as defined in site security plan, are met or trigger events requiring session disconnect. Automatic session termination addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, net
    SV-82609r1_rule SRG-APP-000296-MFP-000007 CCI-002363 MEDIUM Mainframe Products requiring user access authentication must provide a logoff capability for a user-initiated communication session. If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Information resources to which users gain access via authentication include, for example, local
    SV-82611r1_rule SRG-APP-000297-MFP-000008 CCI-002364 MEDIUM The Mainframe Product must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions. If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Users need to be aware of whether or not the session has been terminated. Information resources
    SV-82613r1_rule SRG-APP-000311-MFP-000025 CCI-002262 MEDIUM The Mainframe Product must associate types of security attributes having security attribute values as defined in site security plan with information in storage. Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions representing the basic properties or characteristics of an entity
    SV-82615r1_rule SRG-APP-000313-MFP-000026 CCI-002263 MEDIUM The Mainframe Product must associate types of security attributes having security attribute values as defined in site security plan with information in process. Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions representing the basic properties or characteristics of an entity
    SV-82617r1_rule SRG-APP-000023-MFP-000033 CCI-000015 MEDIUM The Mainframe Product must use an external security manager for all account management functions. Enterprise environments make application account management challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. A comprehensive application account management process that incl
    SV-82619r1_rule SRG-APP-000317-MFP-000034 CCI-002142 MEDIUM The Mainframe Product must terminate shared/group account credentials when members leave the group. If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can still gain access even though they are no longer authorized. A shared/group account credential is a shared form of authentication tha
    SV-82621r1_rule SRG-APP-000024-MFP-000036 CCI-000016 MEDIUM The Mainframe Product must automatically remove or disable temporary user accounts after 72 hours. If temporary user accounts remain active when no longer needed or for an excessive period, these accounts may be used to gain unauthorized access. To mitigate this risk, automated termination of all temporary accounts must be set upon account creation. T
    SV-82623r1_rule SRG-APP-000234-MFP-000037 CCI-001682 MEDIUM The Mainframe Product must be configured such that emergency accounts are never automatically removed or disabled. Emergency accounts are administrator accounts which 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 the
    SV-82625r1_rule SRG-APP-000025-MFP-000038 CCI-000017 MEDIUM The Mainframe Product must automatically disable accounts after 35 days of account inactivity. Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to their user account has been obtained. Applications need t
    SV-82627r1_rule SRG-APP-000026-MFP-000039 CCI-000018 MEDIUM The Mainframe Product must automatically audit account creation. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Auditing of account creation is on
    SV-82629r1_rule SRG-APP-000027-MFP-000040 CCI-001403 MEDIUM The Mainframe Product must automatically audit account modification. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply modify an existing account. Auditing of account modifica
    SV-82631r1_rule SRG-APP-000028-MFP-000041 CCI-001404 MEDIUM The Mainframe Product must automatically audit account disabling actions. When application accounts are disabled, user accessibility is affected. Accounts are used for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events affecting user accessi
    SV-82633r1_rule SRG-APP-000029-MFP-000042 CCI-001405 MEDIUM The Mainframe Product must automatically audit account removal actions. When application accounts are removed, user accessibility is affected. Accounts are used for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events affecting user accessib
    SV-82635r1_rule SRG-APP-000291-MFP-000043 CCI-001683 MEDIUM The Mainframe Product must notify system programmers and security administrators when accounts are created. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Notification of account creation i
    SV-82637r1_rule SRG-APP-000292-MFP-000044 CCI-001684 MEDIUM The Mainframe Product must notify system programmers and security administrators when accounts are modified. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply modify an existing account. Notification of account modi
    SV-82639r1_rule SRG-APP-000293-MFP-000045 CCI-001685 MEDIUM The Mainframe Product must notify system programmers and security administrators for account disabling actions. When application accounts are disabled, user accessibility is affected. Accounts are used for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user acce
    SV-82641r1_rule SRG-APP-000294-MFP-000046 CCI-001686 MEDIUM The Mainframe Product must notify system programmers and security administrators for account removal actions. When application accounts are removed, user accessibility is affected. Accounts are used for identifying individual application users or for identifying the application processes themselves. In order to detect and respond to events that affect user acces
    SV-82643r1_rule SRG-APP-000319-MFP-000047 CCI-002130 MEDIUM The Mainframe Product must automatically audit account enabling actions. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of accoun
    SV-82647r1_rule SRG-APP-000320-MFP-000048 CCI-002132 MEDIUM The Mainframe Product must notify system programmers and security administrators of account enabling actions. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of accoun
    SV-82649r1_rule SRG-APP-000033-MFP-000056 CCI-000213 MEDIUM The Mainframe Product must enforce approved authorizations for logical access to sensitive information and system resources in accordance with applicable access control policies. 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., networks, web servers, and web portals) must be properly configured to incorporate access cont
    SV-82651r1_rule SRG-APP-000033-MFP-000057 CCI-000213 MEDIUM The Mainframe Product must enforce approved authorizations for security administrator access to sensitive information and system resources in accordance with applicable access control policies. 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., networks, web servers, and web portals) must be properly configured to incorporate access cont
    SV-82653r1_rule SRG-APP-000328-MFP-000061 CCI-002165 MEDIUM The Mainframe Product must enforce organization-defined discretionary access control policies over defined subjects and objects. 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
    SV-82655r1_rule SRG-APP-000033-MFP-000066 CCI-000213 MEDIUM The Mainframe Product must enforce approved authorizations for system programmer access to sensitive information and system resources in accordance with applicable access control policies. 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., networks, web servers, and web portals) must be properly configured to incorporate access cont
    SV-82657r1_rule SRG-APP-000038-MFP-000067 CCI-001368 MEDIUM The Mainframe Product must enforce approved authorizations for controlling the flow of information within the system based on site security plan information flow control policies. A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow contro
    SV-82659r1_rule SRG-APP-000340-MFP-000088 CCI-002235 MEDIUM The Mainframe Product must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. 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,
    SV-82661r1_rule SRG-APP-000342-MFP-000090 CCI-002233 MEDIUM The Mainframe Product must prevent software as identified in the site security plan from executing at higher privilege levels than users executing the software. 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 invo
    SV-82663r1_rule SRG-APP-000343-MFP-000091 CCI-002234 MEDIUM The Mainframe Product must audit the execution of privileged functions. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts
    SV-82665r1_rule SRG-APP-000065-MFP-000093 CCI-000044 MEDIUM The Mainframe Product must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period. 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.
    SV-82667r1_rule SRG-APP-000345-MFP-000094 CCI-002238 MEDIUM The Mainframe Product must automatically lock the account until the locked account is released by an administrator when three unsuccessful logon attempts in 15 minutes are exceeded. 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.
    SV-82669r1_rule SRG-APP-000080-MFP-000102 CCI-000166 MEDIUM The Mainframe Product must protect against an individual (or process acting on behalf of an individual) falsely denying having performed actions defined in the site security plan to be covered by non-repudiation. Without non-repudiation, it is impossible to positively attribute an action to an individual (or process acting on behalf of an individual). Non-repudiation services can be used to determine if information originated from a particular individual, or if a
    SV-82671r1_rule SRG-APP-000086-MFP-000110 CCI-000174 MEDIUM For Mainframe Products providing audit record aggregation, the Mainframe Product must compile audit records from mainframe components into a system-wide audit trail that is time-correlated with a tolerance for the relationship between time stamps of individual records in the audit trail in accordance with the sites security plan. Without the ability to collate records based on the time when the events occurred, the ability to perform forensic analysis and investigations across multiple components is significantly degraded. Audit trails are time-correlated if the time stamps in th
    SV-82673r1_rule SRG-APP-000353-MFP-000112 CCI-001914 MEDIUM The Mainframe Product must provide the capability for system programmers to change the auditing to be performed on all application components based on all selectable event criteria within time thresholds defined in the site security plan. If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost. This requirement enable
    SV-82675r1_rule SRG-APP-000353-MFP-000113 CCI-001914 MEDIUM The Mainframe Product must provide the capability for security administrators to change the auditing to be performed on all application components based on all selectable event criteria within time thresholds defined in site security plan. If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to effectively respond, and important forensic information may be lost. This requirement enable
    SV-82677r1_rule SRG-APP-000089-MFP-000114 CCI-000169 MEDIUM The Mainframe Product must provide audit record generation capability for DoD-defined auditable events within all application components. Without the capability to generate audit records, 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
    SV-82679r1_rule SRG-APP-000090-MFP-000115 CCI-000171 MEDIUM The Mainframe Product must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming th
    SV-82681r1_rule SRG-APP-000091-MFP-000116 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to access privileges occur. 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 reco
    SV-82683r1_rule SRG-APP-000492-MFP-000117 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to access security objects occur. 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 rec
    SV-82685r1_rule SRG-APP-000493-MFP-000118 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to access security levels occur. 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 rec
    SV-82687r1_rule SRG-APP-000494-MFP-000119 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. 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 rec
    SV-82689r1_rule SRG-APP-000495-MFP-000120 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to modify privileges occur. 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 rec
    SV-82691r1_rule SRG-APP-000496-MFP-000121 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to modify security objects occur. 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 reco
    SV-82695r1_rule SRG-APP-000497-MFP-000122 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to modify security levels occur. 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 reco
    SV-82697r1_rule SRG-APP-000498-MFP-000123 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. 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 reco
    SV-82699r1_rule SRG-APP-000499-MFP-000124 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to delete privileges occur. 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 reco
    SV-82701r1_rule SRG-APP-000500-MFP-000125 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to delete security levels occur. 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 reco
    SV-82703r1_rule SRG-APP-000501-MFP-000126 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to delete security objects occur. 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 reco
    SV-82705r1_rule SRG-APP-000502-MFP-000127 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful attempts to delete categories of information (e.g., classification levels) occur. 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 reco
    SV-82707r1_rule SRG-APP-000503-MFP-000128 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful logon attempts occur. 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 rec
    SV-82709r1_rule SRG-APP-000504-MFP-000129 CCI-000172 MEDIUM The Mainframe Product must generate audit records for privileged activities or other system-level access. 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 reco
    SV-82711r1_rule SRG-APP-000505-MFP-000130 CCI-000172 MEDIUM The Mainframe Product must generate audit records showing starting and ending time for user access to the system. 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 reco
    SV-82713r1_rule SRG-APP-000506-MFP-000131 CCI-000172 MEDIUM The Mainframe Product must generate audit records when concurrent logons from different workstations occur. 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 reco
    SV-82715r1_rule SRG-APP-000507-MFP-000132 CCI-000172 MEDIUM The Mainframe Product must generate audit records when successful/unsuccessful accesses to objects occur. 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 rec
    SV-82717r1_rule SRG-APP-000508-MFP-000133 CCI-000172 MEDIUM The Mainframe Product must generate audit records for all direct access to the information system. 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 reco
    SV-82719r1_rule SRG-APP-000509-MFP-000134 CCI-000172 MEDIUM The Mainframe Product must generate audit records for all account creations, modifications, disabling, and termination events. 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 reco
    SV-82721r1_rule SRG-APP-000510-MFP-000135 CCI-000172 MEDIUM The Mainframe Product must generate audit records for all kernel module load, unload, and restart events, and for all program initiations. 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 rec
    SV-82723r1_rule SRG-APP-000354-MFP-000136 CCI-001919 MEDIUM The Mainframe Product must provide the capability for authorized users to select a user session to capture/record or view/hear. Without the capability to select a user session to capture/record or view/hear, investigations into suspicious or harmful events would be hampered by the volume of information captured. The volume of information captured may also adversely impact the oper
    SV-82725r1_rule SRG-APP-000092-MFP-000137 CCI-001464 MEDIUM The Mainframe Product must initiate session auditing upon startup. 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.
    SV-82727r1_rule SRG-APP-000093-MFP-000138 CCI-001462 MEDIUM The Mainframe Product must provide the capability for authorized users to capture, record, and log all content related to a user session. Without the capability to capture, record, and log all content related to a user session, investigations into suspicious user activity would be hampered. This requirement does not apply to Mainframe Products that do not have a concept of a user session
    SV-82729r1_rule SRG-APP-000355-MFP-000139 CCI-001920 MEDIUM The Mainframe Product must provide the capability for authorized users to remotely view/hear, in real time, all content related to an established user session from a component separate from the Mainframe Product being monitored. Without the capability to remotely view/hear all content related to a user session, investigations into suspicious user activity would be hampered. Real-time monitoring allows authorized personnel to take action before additional damage is done. The abili
    SV-82731r1_rule SRG-APP-000095-MFP-000140 CCI-000130 MEDIUM The Mainframe Product must produce audit records containing information to establish what type of events occurred. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit record content that may be necessary to satisfy the require
    SV-82733r1_rule SRG-APP-000096-MFP-000141 CCI-000131 MEDIUM The Mainframe Product must produce audit records containing information to establish when (date and time) the events occurred. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personne
    SV-82735r2_rule SRG-APP-000097-MFP-000142 CCI-000132 MEDIUM The Mainframe Product must produce audit records containing information to establish where the events occurred. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. In order to compile an accurate risk assessment, and provide forensic analysis, it is essential for security personn
    SV-82737r1_rule SRG-APP-000098-MFP-000143 CCI-000133 MEDIUM The Mainframe Product must produce audit records containing information to establish the source of the events. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In addition to logging where events occur within the application, the application must also produce audi
    SV-82739r1_rule SRG-APP-000099-MFP-000144 CCI-000134 MEDIUM The Mainframe Product must produce audit records containing information to establish the outcome of the events. Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event succ
    SV-82741r1_rule SRG-APP-000100-MFP-000145 CCI-001487 MEDIUM The Mainframe Product must generate audit records containing information to establish the identity of any individual or process associated with the event. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event. Event identifiers (if
    SV-82743r1_rule SRG-APP-000101-MFP-000146 CCI-000135 MEDIUM The Mainframe Product must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requ
    SV-82745r1_rule SRG-APP-000356-MFP-000147 CCI-001844 MEDIUM The Mainframe Product must provide centralized management and configuration of the content to be captured in audit records generated by all application components. Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. This re
    SV-82747r1_rule SRG-APP-000357-MFP-000148 CCI-001849 MEDIUM The mainframe product must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. In order to ensure applications have a sufficient storage capacity in which to write the audit logs, applications need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during
    SV-82749r1_rule SRG-APP-000358-MFP-000149 CCI-001851 MEDIUM The Mainframe Product must off-load audit records onto a different system or media than the system being audited. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity.
    SV-82751r1_rule SRG-APP-000359-MFP-000151 CCI-001855 MEDIUM The Mainframe Product must provide an immediate warning to the system programmer and security administrator (at a minimum) when allocated audit record storage volume reaches 75 percent of repository maximum audit record storage capacity. If security personnel are not notified immediately upon storage volume utilization reaching 75 percent, they are unable to plan for storage capacity expansion.
    SV-82753r1_rule SRG-APP-000360-MFP-000152 CCI-001858 MEDIUM The Mainframe Product must provide an immediate real-time alert to the operations staff, system programmers, and/or security administrators, at a minimum, of all audit failure events requiring real-time alerts. It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation
    SV-82755r1_rule SRG-APP-000108-MFP-000154 CCI-000139 MEDIUM The Mainframe Product must alert the SA and ISSO (at a minimum) in the event of an audit processing failure. It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability and system opera
    SV-82757r1_rule SRG-APP-000109-MFP-000155 CCI-000140 MEDIUM The Mainframe Product must shut down by default upon audit failure (unless availability is an overriding concern). It is critical that when the application is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit st
    SV-82759r1_rule SRG-APP-000111-MFP-000156 CCI-000154 MEDIUM The Mainframe Product must provide the capability to centrally review and analyze audit records from multiple components within the system. Successful incident response and auditing relies on timely, accurate system information and analysis in order to allow the organization to identify and respond to potential incidents in a proficient manner. If the application does not provide the ability
    SV-82761r1_rule SRG-APP-000115-MFP-000157 CCI-000158 MEDIUM The Mainframe Products must provide the capability to filter audit records for events of interest as defined in site security plan. The ability to specify the event criteria that are of interest provides the persons reviewing the logs with the ability to quickly isolate and identify these events without having to review entries that are of little or no consequence to the investigation
    SV-82763r1_rule SRG-APP-000364-MFP-000160 CCI-001875 MEDIUM The Mainframe Product must provide an audit reduction capability that supports on-demand audit review and analysis. The ability to perform on-demand audit review and analysis, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more c
    SV-82765r1_rule SRG-APP-000181-MFP-000161 CCI-001876 MEDIUM The Mainframe Product must provide an audit reduction capability that supports on-demand reporting requirements. The ability to generate on-demand reports, including after the audit data has been subjected to audit reduction, greatly facilitates the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security i
    SV-82767r1_rule SRG-APP-000365-MFP-000162 CCI-001877 MEDIUM The Mainframe Product must provide an audit reduction capability that supports after-the-fact investigations of security incidents. If the audit reduction capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack, or identify those responses for one. This capability is also required
    SV-82769r1_rule SRG-APP-000366-MFP-000163 CCI-001878 MEDIUM The Mainframe Product must provide a report generation capability that supports on-demand audit review and analysis. The report generation capability must support on-demand review and analysis in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents. Report generation must
    SV-82771r1_rule SRG-APP-000367-MFP-000164 CCI-001879 MEDIUM The Mainframe Product must provide a report generation capability that supports on-demand reporting requirements. The report generation capability must support on-demand reporting in order to facilitate the organization's ability to generate incident reports as needed to better handle larger-scale or more complex security incidents The report generation capability p
    SV-82773r1_rule SRG-APP-000368-MFP-000165 CCI-001880 MEDIUM The Mainframe Product must provide a report generation capability that supports after-the-fact investigations of security incidents. If the report generation capability does not support after-the-fact investigations, it is difficult to establish, correlate, and investigate the events leading up to an outage or attack, or identify those responses for one. This capability is also require
    SV-82775r1_rule SRG-APP-000369-MFP-000166 CCI-001881 MEDIUM The Mainframe Product must provide an audit reduction capability that does not alter original content or time ordering of audit records. If the audit reduction capability alters the content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronological organization o
    SV-82777r1_rule SRG-APP-000370-MFP-000167 CCI-001882 MEDIUM The Mainframe Product must provide a report generation capability that does not alter original content or time ordering of audit records. If the audit report generation capability alters the original content or time ordering of audit records, the integrity of the audit records is compromised, and the records are no longer usable for forensic analysis. Time ordering refers to the chronologic
    SV-82779r1_rule SRG-APP-000116-MFP-000171 CCI-000159 MEDIUM The Mainframe Products must use internal system clocks to generate time stamps for audit records. Without an internal clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when
    SV-82781r1_rule SRG-APP-000118-MFP-000174 CCI-000162 MEDIUM The Mainframe Product must protect audit information from any type of unauthorized read access. If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In addition, access to audit records provides information an at
    SV-82783r1_rule SRG-APP-000119-MFP-000175 CCI-000163 MEDIUM The Mainframe Product must protect audit information from unauthorized modification. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must
    SV-82785r1_rule SRG-APP-000120-MFP-000176 CCI-000164 MEDIUM The Mainframe Product must protect audit information from unauthorized deletion. If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracity of audit data, the information system and/or the application must
    SV-82787r1_rule SRG-APP-000121-MFP-000177 CCI-001493 MEDIUM The Mainframe Product must protect audit tools from unauthorized access. Protecting audit data 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 data. Applications providing tools to interface with
    SV-82789r1_rule SRG-APP-000122-MFP-000178 CCI-001494 MEDIUM The Mainframe Product must protect audit tools from unauthorized modification. Protecting audit data 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 data. Applications providing tools to interface with
    SV-82791r1_rule SRG-APP-000123-MFP-000179 CCI-001495 MEDIUM The Mainframe Product must protect audit tools from unauthorized deletion. Protecting audit data 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 data. Applications providing tools to interface with
    SV-82793r1_rule SRG-APP-000290-MFP-000182 CCI-001496 MEDIUM The Mainframe Product must use cryptographic mechanisms to protect the integrity of audit tools. Protecting the integrity of the tools used for auditing purposes is a critical step to ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit informat
    SV-82795r1_rule SRG-APP-000378-MFP-000185 CCI-001812 MEDIUM The Mainframe product must prohibit user installation of software without explicit privileged status. 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 use
    SV-82797r1_rule SRG-APP-000379-MFP-000186 CCI-001744 MEDIUM The Mainframe Product must implement organization-defined automated security responses if baseline configurations are changed in an unauthorized manner. Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the system. Changes to information system configurations can have unintended side effects, some of which may be relevant
    SV-82799r1_rule SRG-APP-000380-MFP-000187 CCI-001813 MEDIUM The Mainframe Product must enforce access restrictions associated with changes to application configuration. Failure to provide logical access restrictions associated with changes to application configuration may have significant effects on the overall security of the system. When dealing with access restrictions pertaining to change control, it should be note
    SV-82801r1_rule SRG-APP-000381-MFP-000188 CCI-001814 MEDIUM The Mainframe Product must audit the enforcement actions used to restrict access associated with changes to the application. Without auditing the enforcement of access restrictions against changes to the application configuration, it will be difficult to identify attempted attacks and an audit trail will not be available for forensic investigation for after-the-fact actions.
    SV-82803r1_rule SRG-APP-000131-MFP-000189 CCI-001749 MEDIUM The Mainframe Product must prevent the installation of patches, service packs, or application components without verification that the software component has been digitally signed using a certificate that is recognized and approved by the organization. Changes to any software components can have significant effects on the overall security of the application. Verifying software components have been digitally signed using a certificate that is recognized and approved by the organization ensures the softwa
    SV-82805r1_rule SRG-APP-000133-MFP-000192 CCI-001499 MEDIUM The Mainframe Product must limit privileges to change the Mainframe Product installation datasets to system programmers and authorized users in accordance with applicable access control policies. If the application 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 applie
    SV-82807r1_rule SRG-APP-000133-MFP-000193 CCI-001499 MEDIUM The Mainframe Product must limit privileges to change Mainframe Product started task and job datasets to system programmers and authorized users in accordance with applicable access control policies. If the application 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 applie
    SV-82809r1_rule SRG-APP-000133-MFP-000194 CCI-001499 MEDIUM The Mainframe Product must limit privileges to change Mainframe Product user datasets to authorized individuals. If the application 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 applie
    SV-82811r1_rule SRG-APP-000516-MFP-000195 CCI-000366 MEDIUM The Mainframe Product must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. Configuring the application 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 p
    SV-82815r1_rule SRG-APP-000141-MFP-000200 CCI-000381 MEDIUM The Mainframe Product must be configured to disable non-essential capabilities. It is detrimental for applications 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
    SV-82817r1_rule SRG-APP-000389-MFP-000204 CCI-002038 MEDIUM The Mainframe Product must require users to reauthenticate when circumstances or situations require reauthentication as defined in site security plan. Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical th
    SV-82819r1_rule SRG-APP-000390-MFP-000205 CCI-002039 MEDIUM The Mainframe Product must require devices to reauthenticate when circumstances or situations require reauthentication as defined in site security plan. Without reauthenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of de
    SV-82821r1_rule SRG-APP-000148-MFP-000206 CCI-000764 MEDIUM The Mainframe Product must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the org
    SV-82823r1_rule SRG-APP-000149-MFP-000207 CCI-000765 MEDIUM The Mainframe Product must use multifactor authentication for network access to privileged accounts. Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) something a user knows (e.g.
    SV-82825r1_rule SRG-APP-000391-MFP-000208 CCI-001953 MEDIUM The Mainframe Product must accept Personal Identity Verification (PIV) credentials. The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary com
    SV-82827r1_rule SRG-APP-000392-MFP-000209 CCI-001954 MEDIUM The Mainframe Product must electronically verify Personal Identity Verification (PIV) credentials. The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DoD has mandated the use of the CAC to support identity management and personal authentication for systems covered under HSPD 12, as well as a primary com
    SV-82829r1_rule SRG-APP-000150-MFP-000211 CCI-000766 MEDIUM The Mainframe Product must use multifactor authentication for network access to non-privileged accounts. To assure accountability and prevent unauthenticated access, non-privileged users must use multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication uses two or more factors to achieve authentication
    SV-82859r1_rule SRG-APP-000153-MFP-000214 CCI-000770 MEDIUM The Mainframe Product must verify users are authenticated with an individual authenticator prior to using a group authenticator. To assure individual accountability and prevent unauthorized access, application users must be individually identified and authenticated. Individual accountability mandates that each user is uniquely identified. A group authenticator is a shared account
    SV-82861r1_rule SRG-APP-000164-MFP-000227 CCI-000205 MEDIUM The Mainframe Product must enforce a minimum 15-character password length. 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 bru
    SV-82863r1_rule SRG-APP-000166-MFP-000228 CCI-000192 MEDIUM The Mainframe Product must enforce password complexity by requiring that at least one uppercase character be used. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password
    SV-82865r1_rule SRG-APP-000167-MFP-000229 CCI-000193 MEDIUM The Mainframe Product must enforce password complexity by requiring that at least one lowercase character be used. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password
    SV-82867r1_rule SRG-APP-000168-MFP-000230 CCI-000194 MEDIUM The Mainframe Product must enforce password complexity by requiring that at least one numeric character be used. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password
    SV-82871r1_rule SRG-APP-000169-MFP-000231 CCI-001619 MEDIUM The Mainframe Product must enforce password complexity by requiring that at least one special character be used. Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password
    SV-82873r1_rule SRG-APP-000170-MFP-000232 CCI-000195 MEDIUM The Mainframe Product must require the change of at least 8 of the total number of characters when passwords are changed. If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. The number of changed c
    SV-82875r1_rule SRG-APP-000171-MFP-000233 CCI-000196 MEDIUM The Mainframe Product must store only cryptographically protected passwords. 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. Applications must enforce password encryption
    SV-82877r1_rule SRG-APP-000172-MFP-000234 CCI-000197 MEDIUM The Mainframe Product must transmit only cryptographically protected passwords. 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. Applications can accomplish this by making dir
    SV-82879r1_rule SRG-APP-000173-MFP-000235 CCI-000198 MEDIUM The Mainframe Product must enforce 24 hours/1 day as the minimum password lifetime. Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. Restricting this setting limits the user's ability to change their password. Passwords need to be changed at sp
    SV-82881r1_rule SRG-APP-000174-MFP-000236 CCI-000199 MEDIUM The Mainframe Product must enforce a 60-day maximum password lifetime restriction. Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals. One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit
    SV-82883r1_rule SRG-APP-000165-MFP-000237 CCI-000200 MEDIUM The Mainframe Product must prohibit password reuse for a minimum of five generations. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. To meet password policy requirements, passwords need to be changed at specific policy-based intervals. If the
    SV-82885r1_rule SRG-APP-000397-MFP-000238 CCI-002041 MEDIUM The Mainframe Product must allow the use of a temporary password for system logons with an immediate change to a permanent password. Without providing this capability, an account may be created without a password. Non-repudiation cannot be guaranteed once an account is created if a user is not forced to change the temporary password upon initial logon. Temporary passwords are typical
    SV-82887r1_rule SRG-APP-000400-MFP-000241 CCI-002007 MEDIUM The Mainframe Product must prohibit the use of cached authenticators after one hour. If cached authentication information is out of date, the validity of the authentication information may be questionable.
    SV-82889r1_rule SRG-APP-000175-MFP-000242 CCI-000185 MEDIUM The Mainframe Product, when using PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. 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
    SV-82891r1_rule SRG-APP-000176-MFP-000243 CCI-000186 MEDIUM The Mainframe Product, when using PKI-based authentication, must enforce authorized access to the corresponding private key. 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 priva
    SV-82893r1_rule SRG-APP-000177-MFP-000244 CCI-000187 MEDIUM The Mainframe Product must map the authenticated identity to the individual user or group account for PKI-based authentication. Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.
    SV-82895r1_rule SRG-APP-000178-MFP-000246 CCI-000206 MEDIUM The Mainframe Product must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. To prevent the compromise of authentication information such as passwords during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication m
    SV-82897r1_rule SRG-APP-000179-MFP-000247 CCI-000803 MEDIUM The Mainframe Product must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confidentiality or integrity, and DoD data may be compromised. Applications using encryption are required to
    SV-82899r1_rule SRG-APP-000180-MFP-000248 CCI-000804 MEDIUM The Mainframe Product must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). Lack of authentication and identification enables non-organizational users to gain access to the application or possibly other information systems and provides an opportunity for intruders to compromise resources within the application or information syst
    SV-82901r1_rule SRG-APP-000402-MFP-000249 CCI-002009 MEDIUM The Mainframe Product must accept Personal Identity Verification (PIV) credentials from other federal agencies. Access may be denied to authorized users if federal agency PIV credentials are not accepted. PIV credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance documents. OMB Memorandum 11-11 re
    SV-82903r1_rule SRG-APP-000403-MFP-000250 CCI-002010 MEDIUM The Mainframe Product must electronically verify Personal Identity Verification (PIV) credentials from other federal agencies. Inappropriate access may be granted to unauthorized users if federal agency PIV credentials are not electronically verified. PIV credentials are those credentials issued by federal agencies that conform to FIPS Publication 201 and supporting guidance do
    SV-82905r1_rule SRG-APP-000404-MFP-000251 CCI-002011 MEDIUM The Mainframe Product must accept FICAM-approved third-party credentials. Access may be denied to legitimate users if FICAM-approved third-party credentials are not accepted. This requirement typically applies to organizational information systems that are accessible to non-federal government agencies and other partners. This
    SV-82907r1_rule SRG-APP-000405-MFP-000252 CCI-002014 MEDIUM The Mainframe Product must conform to FICAM-issued profiles. Without conforming to FICAM-issued profiles, the information system may not be interoperable with FICAM-authentication protocols, such as SAML 2.0 and OpenID 2.0. This requirement addresses open identity management standards.
    SV-82909r1_rule SRG-APP-000073-MFP-000255 CCI-000870 MEDIUM Mainframe Products scanning for malicious code must scan all media used for system maintenance prior to use. There are security-related issues arising from software brought into the information system specifically for diagnostic and repair actions (e.g., a software packet sniffer installed on a system in order to troubleshoot system traffic, or a vendor installi
    SV-82911r1_rule SRG-APP-000409-MFP-000257 CCI-002884 MEDIUM Mainframe Products must audit nonlocal maintenance and diagnostic sessions audit events as defined in site security plan. If events associated with nonlocal administrative access or diagnostic sessions are not logged and audited, a major tool for assessing and investigating attacks would not be available. This requirement addresses auditing-related issues associated with ma
    SV-82913r1_rule SRG-APP-000411-MFP-000260 CCI-002890 MEDIUM Mainframe Products must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications. Privileged access contains control and configuration information which is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms to protect integrity. Nonlocal maintenance and diagnostic acti
    SV-82915r1_rule SRG-APP-000412-MFP-000261 CCI-003123 MEDIUM Mainframe Products must implement cryptographic mechanisms to protect the confidentiality of nonlocal maintenance and diagnostic communications. Privileged access contains control and configuration information which is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms to protect confidentiality. Nonlocal maintenance and diagnosti
    SV-82917r1_rule SRG-APP-000413-MFP-000262 CCI-002891 MEDIUM Mainframe Products must verify remote disconnection at the termination of nonlocal maintenance and diagnostic sessions. If the remote connection is not closed and verified as closed, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Remote connections must be disconnected and verified as disconnected when nonlocal mainten
    SV-82919r1_rule SRG-APP-000186-MFP-000264 CCI-000879 MEDIUM The Mainframe Product must terminate all sessions and network connections when nonlocal maintenance is completed. If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and used to compromise or damage the system. Nonlocal maintenance and diagnostic activities are those activities conducted by individual
    SV-82921r1_rule SRG-APP-000414-MFP-000265 CCI-001067 MEDIUM The Mainframe Product must implement privileged access authorization to all information systems and infrastructure components for selected vulnerability scanning activities as defined in the site security plan. In certain situations, the nature of the vulnerability scanning may be more intrusive, or the information system component that is the subject of the scanning may contain highly sensitive information. Privileged access authorization to selected system com
    SV-82923r1_rule SRG-APP-000416-MFP-000269 CCI-002450 MEDIUM The Mainframe Product must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive orders, directives, policies, regulations, and standards. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assuran
    SV-82925r1_rule SRG-APP-000514-MFP-000270 CCI-002450 MEDIUM The Mainframe Product must implement NIST FIPS-validated cryptography to provision digital signatures in accordance with applicable federal laws, Executive orders, directives, policies, regulations, and standards. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assuran
    SV-82927r1_rule SRG-APP-000514-MFP-000272 CCI-002450 MEDIUM The Mainframe Product must implement NIST FIPS-validated cryptography to generate and validate cryptographic hashes in accordance with applicable federal laws, Executive orders, directives, policies, regulations, and standards. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assuran
    SV-82929r1_rule SRG-APP-000514-MFP-000274 CCI-002450 MEDIUM The Mainframe Product must implement NIST FIPS-validated cryptography to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive orders, directives, policies, regulations, and standards. Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assuran
    SV-82935r1_rule SRG-APP-000206-MFP-000277 CCI-001166 MEDIUM The Mainframe Product must identify prohibited mobile code. Decisions regarding the employment of mobile code within applications are based on the potential for the code to cause damage to the system if used maliciously. Mobile code is defined as software modules obtained from remote systems, transferred across
    SV-82937r1_rule SRG-APP-000207-MFP-000278 CCI-001662 MEDIUM The Mainframe Product must block, quarantine, and/or alert system administrators when prohibited mobile code is identified. Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. Mobile code is defined as software modules obtained from remote system
    SV-82939r1_rule SRG-APP-000209-MFP-000279 CCI-001169 MEDIUM The Mainframe Product must prevent the download of prohibited mobile code. Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. Mobile code is defined as software modules obtained from remote system
    SV-82941r1_rule SRG-APP-000112-MFP-000280 CCI-001695 MEDIUM The Mainframe Product must prevent the execution of prohibited mobile code. Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. Mobile code is defined as software modules obtained from remote system
    SV-82943r1_rule SRG-APP-000210-MFP-000281 CCI-001170 MEDIUM The Mainframe Product must prevent the automatic execution of mobile code in, at a minimum, office applications, browsers, email clients, mobile code run-time environments, and mobile agent systems. Mobile code can cause damage to the system. It can execute without explicit action from, or notification to, a user. Preventing automatic execution of mobile code includes, for example, disabling auto execute features on information system components.
    SV-82945r1_rule SRG-APP-000488-MFP-000282 CCI-002460 MEDIUM The Mainframe Product must prompt the user for action prior to executing mobile code. Mobile code can cause damage to the system. It can execute without explicit action from, or notification to, a user. Actions enforced before executing mobile code include, for example, prompting users prior to opening email attachments and disabling aut
    SV-82947r1_rule SRG-APP-000211-MFP-000283 CCI-001082 MEDIUM The Mainframe Product must separate user functionality (including user interface services) from information system management functionality. Application management functionality includes functions necessary for administration and requires privileged user access. Allowing non-privileged users to access application management functionality capabilities increases the risk that non-privileged user
    SV-82949r1_rule SRG-APP-000225-MFP-000300 CCI-001190 MEDIUM The Mainframe Product must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Applications or systems that fail suddenly and with no incorporated failure state planning may leave the ho
    SV-82951r1_rule SRG-APP-000226-MFP-000301 CCI-001665 MEDIUM In the event of application failure, Mainframe Products must preserve any information necessary to determine the cause of failure and any information necessary to return to operations with the least disruption to mission processes. Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the
    SV-82953r1_rule SRG-APP-000231-MFP-000302 CCI-001199 MEDIUM The Mainframe Product must protect the confidentiality and integrity of all information at rest. 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) within an organizational information system. Mobile devices, laptops, desktops, and storage devices can be either los
    SV-82955r1_rule SRG-APP-000428-MFP-000303 CCI-002475 MEDIUM The Mainframe Product must implement cryptographic mechanisms to prevent unauthorized modification of all information not cleared for public release at rest on system components outside of organization facilities. Applications 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 th
    SV-82957r1_rule SRG-APP-000429-MFP-000304 CCI-002476 MEDIUM The Mainframe Product must implement cryptographic mechanisms to prevent unauthorized disclosure of all information not cleared for public release at rest on system components outside of organization facilities. Applications 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 th
    SV-82959r1_rule SRG-APP-000233-MFP-000305 CCI-001084 MEDIUM The Mainframe Product must isolate security functions from nonsecurity functions. 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 en
    SV-82961r1_rule SRG-APP-000431-MFP-000312 CCI-002530 MEDIUM The Mainframe Product must maintain a separate execution domain for each executing process. Applications can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is performed in a manner controlled throu
    SV-82963r1_rule SRG-APP-000251-MFP-000328 CCI-001310 MEDIUM The Mainframe Product must check the validity of all data inputs except those specifically identified by the organization. Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or i
    SV-82965r1_rule SRG-APP-000447-MFP-000332 CCI-002754 MEDIUM The Mainframe Product must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. A common vulnerability of applications is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may
    SV-82967r1_rule SRG-APP-000266-MFP-000334 CCI-001312 MEDIUM The Mainframe Product must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. Any application providing too much information in error messages risks compromising the data and security of the application and system. The structure and content of error messages needs to be carefully considered by the organization and development team.
    SV-82969r1_rule SRG-APP-000267-MFP-000335 CCI-001314 MEDIUM The Mainframe Product must reveal full-text detail error messages only to system programmers and/or security administrators. Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify the application. Additionally, Personally Identifiable Information (PII) and operatio
    SV-82971r1_rule SRG-APP-000450-MFP-000338 CCI-002824 MEDIUM The Mainframe Product must implement security safeguards to protect its memory from unauthorized code execution. Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Security safeguards employed to protect memory include, for example, data execution prevention and address sp
    SV-82973r1_rule SRG-APP-000454-MFP-000343 CCI-002617 MEDIUM The Mainframe Product must remove all upgraded/replaced software components that are no longer required for operation after updated versions have been installed. Previous versions of software components that are not removed from the information system after updates have been installed may be exploited by adversaries. Some information technology products may remove older versions of software automatically from the
    SV-82975r1_rule SRG-APP-000456-MFP-000345 CCI-002605 MEDIUM The Mainframe Product must install security-relevant software updates within the time period directed by an authoritative source (e.g., IAVMs, CTOs, DTMs, and STIGs). Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to
    SV-82977r1_rule SRG-APP-000272-MFP-000347 CCI-001247 MEDIUM The Mainframe Product must automatically update malicious code protection mechanisms. Malicious software detection applications need to be constantly updated in order to identify new threats as they are discovered. All malicious software detection software must come with an update mechanism that automatically updates the application and
    SV-82979r1_rule SRG-APP-000276-MFP-000353 CCI-001240 MEDIUM The Mainframe Product must update malicious code protection mechanisms whenever new releases are available in accordance with organizational configuration management policy and procedures. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code specific to mainframes may be any code that corrupts system files. The code provides the ability for a malicious user to read from and write to files and folders on a compu
    SV-82981r1_rule SRG-APP-000277-MFP-000354 CCI-001241 MEDIUM The Mainframe Product must configure malicious code protection mechanisms to perform periodic scans of the information system every seven days. Malicious code protection mechanisms include, but are not limited to, anti-virus and malware detection software. Malicious code protection mechanisms specific to Mainframe Products are designed to periodically scan system files to validate their integrity
    SV-82983r1_rule SRG-APP-000472-MFP-000370 CCI-002696 MEDIUM The Mainframe Product performing organization-defined security functions must verify correct operation of security functions. Without verification, security functions may not operate correctly and this 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
    SV-82985r1_rule SRG-APP-000473-MFP-000371 CCI-002699 MEDIUM The Mainframe Product must perform verification of the correct operation of security functions upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days. Without verification, security functions may not operate correctly and this 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
    SV-82987r1_rule SRG-APP-000275-MFP-000372 CCI-001294 MEDIUM The Mainframe product must notify the system programmer and security administrator of failed security verification tests. If personnel are not notified of failed security verification tests, they will not be able to take corrective action and the unsecure condition(s) will remain. Security function is defined as the hardware, software, and/or firmware of the information sy
    SV-82989r1_rule SRG-APP-000474-MFP-000373 CCI-002702 MEDIUM The Mainframe Product must either shut down, restart, and/or notify the appropriate personnel when anomalies in the operation of the security functions as defined in site security plan are discovered. If anomalies are not acted on, security functions may fail to secure the system. Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the is
    SV-82991r1_rule SRG-APP-000475-MFP-000374 CCI-002710 MEDIUM The Mainframe product must perform an integrity check of all software from vendors/sources that provide cryptographic mechanisms to enable the validation of code authenticity and integrity at startup, at transitional states as defined in site security plan or security-relevant events, or annually. Unauthorized changes to software can occur due to errors or malicious activity (e.g., tampering). Software includes, for example, operating systems (with key internal components such as kernels, drivers), middleware, and applications. State-of-the-practic
    SV-82993r1_rule SRG-APP-000477-MFP-000376 CCI-002712 MEDIUM The Mainframe Product must perform an integrity check of information as defined in site security plan at startup, at transitional states as defined in site security plan or security-relevant events, or annually. Unauthorized changes to information can occur due to errors or malicious activity (e.g., tampering). Information includes metadata, such as security attributes associated with information. State-of-the-practice integrity-checking mechanisms (e.g., parity
    SV-82995r1_rule SRG-APP-000480-MFP-000379 CCI-002715 MEDIUM The Mainframe Product must automatically shut down the information system, restart the information system, and/or implement security safeguards as conditions as defined in site security plan when integrity violations are discovered. Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity (e.g., tampering). Information includes metadata, such as security attributes associated with information. State-of-the-practice integrity-checking m
    SV-82997r1_rule SRG-APP-000484-MFP-000383 CCI-002723 MEDIUM The Mainframe Product must audit detected potential integrity violations. Without an audit capability, an integrity violation may not be detected. Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations. The integrity verification app
    SV-82999r1_rule SRG-APP-000485-MFP-000384 CCI-002724 MEDIUM The Mainframe Product, upon detection of a potential integrity violation, must initiate one or more of the following actions: generate an audit record, alert the current user, alert personnel or roles as defined in the site security plan, and/or perform other actions as defined in site security plan. Without an audit capability, an integrity violation may not be detected. Organizations select response actions based on types of software, specific software, or information for which there are potential integrity violations. The integrity verification app
    SV-83001r1_rule SRG-APP-000151-MFP-000212 CCI-000767 MEDIUM The Mainframe Product must use multifactor authentication for local access to privileged accounts. To assure accountability and prevent unauthenticated access, privileged users must use multifactor authentication to prevent potential misuse and compromise of the system. Multifactor authentication is defined as: using two or more factors to achieve au
    SV-83003r2_rule SRG-APP-000152-MFP-000213 CCI-000768 MEDIUM The Mainframe Product must use multifactor authentication for local access to non-privileged accounts. To assure accountability, prevent unauthenticated access, and prevent misuse of the system, non-privileged users must use multifactor authentication for local access. Multifactor authentication is defined as: using two or more factors to achieve authent