The Mainframe Product must notify system programmers and security administrators of account enabling actions.

STIG ID: SRG-APP-000320-MFP-000048  |  SRG: SRG-APP-000320 |  Severity: medium |  CCI: CCI-000015 |  Vulnerability Id: V-205542 | 

Vulnerability Discussion

Once an attacker establishes access to an application, 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. Sending notification of account enabling events to the system administrator (SA) and information system security officer (ISSO) is one method for mitigating this risk. Such a capability greatly reduces the risk that application accessibility will be negatively affected for extended periods of time and also provides logging that can be used for forensic purposes.

To detect and respond to events that affect user accessibility and application processing, applications must notify the appropriate individuals so they can investigate the event.

To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. Such integration allows the application developer to offload those access control functions and focus on core application features and functionality.

Check

If the Mainframe Product employs an external security manager for all account management functions, this is not applicable.

Examine account management settings.

If the Mainframe Product does not notify system programmers and security administrators of account enabling actions, this is a finding.

Fix

Configure the Mainframe Product account management settings to notify system programmers and security administrators of account enabling actions.