The application must generate audit records when successful/unsuccessful logon attempts occur.

From Application Security and Development Security Technical Implementation Guide

Associated with: CCI-000172

SV-84027r1_rule The application must generate audit records when successful/unsuccessful logon attempts 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).Knowing when a user successfully or unsuccessfully logged on to the application is critical information that aids in forensic analysis.

Check content

Review and monitor the application logs. Authenticate to the application and observe if the log includes an entry to indicate the user’s authentication was successful. Terminate the user session by logging out. Reauthenticate using invalid user credentials and observe if the log includes an entry to indicate the authentication was unsuccessful. If successful and unsuccessful logon events are not recorded in the logs, this is a finding.

Fix text

Configure the application or application server to write a log entry when successful and unsuccessful logon events occur.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.