Rule ID
SV-288198r1252973_rule
Version
V1R0.1
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 simply modify an existing account. Auditing of account creation is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail documents the creation of application user accounts and, as required, notifies administrators and/or application owners it exists. Such a process greatly reduces the risk that accounts will be surreptitiously created 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 meeting or exceeding access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality.
Review the application documentation and deployed configuration to determine whether the application's authentication mechanism audits account modifications to include disabling/removal actions, and attempts to access privileges. If the application's authentication mechanism does not audit account modifications to include disabling/removal actions and attempts to access privileges, this is a finding.
Navigate to the authentication configuration function within the application. Configure the application's authentication mechanism to audit account modifications to include disabling/removal actions, and attempts to access privileges.