The application must generate audit records when successful/unsuccessful attempts to modify privileges occur.

From Application Security and Development Security Technical Implementation Guide

Part of SRG-APP-000495

Associated with: CCI-000172

SV-84011r1_rule The application must generate audit records when successful/unsuccessful attempts to modify privileges occur.

Vulnerability discussion

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).

Check content

Review the application documentation and interview the application admin to identify application management interfaces and features. Access the application management utility and create a test user account or use the account of a regular privileged user who is cooperating with the testing. Access and open the auditing logs. Using an admin account, modify the privileges of a privileged user. Attempt to modify privileges in a manner that will cause a failure event such as attempting to modify a user’s privileges with an account that doesn't have the rights to do so. Review the application logs and ensure both events were captured in the logs. The event data should include the user’s identity and the privilege that was granted and the privilege that failed to be granted. If the application does not log when successful and unsuccessful attempts to modify privileges occur, this is a finding.

Fix text

Configure the application to audit successful and unsuccessful attempts to modify privileges.

Pro Tips

Powered by sagemincer