Title

The application must generate audit records when successful/unsuccessful accesses to objects occur. (Cat II impact)

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. Application objects are system or application components that comprise the application. This includes but is not limited to; application files, folders, processes and modules. This requirement is not intended to force the use of debug logging which would be used for troubleshooting or forensic actions; rather it is intended to assure the application strikes a balance when auditing access to application objects and logs normal and potentially abnormal application activity. 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 administrator to identify log locations. Access the application logs. Review the logs and identify if the application is logging both successful and unsuccessful access to application objects such as files, folders, processes, or application modules and sub components, or systems. If the application does not log application object access, this is a finding.

Fix Text

Configure the application to log successful and unsuccessful access to application objects.

Additional Identifiers

Rule ID: SV-222465r879878_rule

Vulnerability ID: V-222465

Group Title: SRG-APP-000507

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.