UCF STIG Viewer Logo

The vAMI error logs must be reviewed.


Overview

Finding ID Version Rule ID IA Controls Severity
V-90239 VRAU-VA-000340 SV-100889r1_rule Medium
Description
The structure and content of error messages need to be carefully considered by the organization and development team. Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The extent to which the application server is able to identify and handle error conditions is guided by organizational policy and operational requirements. Adequate logging levels and system performance capabilities need to be balanced with data protection requirements. The structure and content of error messages needs to be carefully considered by the organization and development team. Application servers must have the capability to log at various levels, which can provide log entries for potential security-related error events. An example is the capability for the application server to assign a criticality level to a failed logon attempt error message, a security-related error message being of a higher criticality.
STIG Date
VMW vRealize Automation 7.x vAMI Security Technical Implementation Guide 2018-10-12

Details

Check Text ( C-89931r1_chk )
Interview the ISSO and/or the SA and review vRA product documentation.

Determine a local procedure exists for monitoring error conditions reported by the vAMI.

If a procedure does not exist or is not being followed, this is a finding.
Fix Text (F-96981r1_fix)
Develop and implement a site procedure to monitor error conditions reported by the vAMI.