The application must notify system administrators (SAs) and information system security officers (ISSOs) of account removal actions.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-222420	APSC-DV-000410	SV-222420r985914_rule		Low

Description
Once an attacker establishes 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 remove an account. Notification of account removal is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the removal of application user accounts and notifies administrators and ISSOs such accounts no longer exist. This type of process greatly reduces the risk that accounts will be surreptitiously removed and provides logging that can be used for forensic purposes. 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.

Description

Once an attacker establishes 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 remove an account. Notification of account removal is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the removal of application user accounts and notifies administrators and ISSOs such accounts no longer exist. This type of process greatly reduces the risk that accounts will be surreptitiously removed and provides logging that can be used for forensic purposes. 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.

STIG	Date
Application Security and Development Security Technical Implementation Guide	2024-06-05

Details

Check Text ( C-24090r985912_chk )
Review the application and system documentation. Interview the application administrator and determine if the application is configured to utilize a centralized user management system like Active Directory for user management or if the application manages user accounts within the application. If the application is configured to use an enterprise-based application user management capability that is STIG compliant, the requirement is Not Applicable. Ensure the application is configured to notify SAs when accounts are removed by identifying the SAs who will be notified when accounts are removed. Remove a test account and check with a SA to verify the notification was received. If SAs and ISSOs are not notified when accounts are removed, this is a finding.

Check Text ( C-24090r985912_chk )

Review the application and system documentation.

Interview the application administrator and determine if the application is configured to utilize a centralized user management system like Active Directory for user management or if the application manages user accounts within the application.

If the application is configured to use an enterprise-based application user management capability that is STIG compliant, the requirement is Not Applicable.

Ensure the application is configured to notify SAs when accounts are removed by identifying the SAs who will be notified when accounts are removed.

Remove a test account and check with a SA to verify the notification was received.

If SAs and ISSOs are not notified when accounts are removed, this is a finding.

Fix Text (F-24079r985913_fix)
Configure the application to notify the SA and the ISSO when application accounts are removed.