Rule ID
SV-286599r1290960_rule
Version
V1R1
CCIs
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 structure and content of error messages must be carefully considered by the organization and development team. The application server must not log sensitive information such as passwords, private keys, or other sensitive data. This requirement pertains to logs that are generated by the application server and application server processes, not the applications that may reside on the application server. Those errors are out of the scope of these requirements.
Log in to the UAG administrative interface as an administrator. Select "Configure Manually". Navigate to Support Settings >> Log Level Settings. Click the gear icon to edit. If the log level settings does not contain an entry for "All - INFO", this is a finding. Note: "DEBUG" and "TRACE" log levels must be applied only during troubleshooting as these levels can reduce performance and increase the verbose log messages. After troubleshooting using the DEBUG or TRACE log levels, the log level must be reset to INFO or the component or subcomponent must be removed from the log settings.
Log in to the UAG administrative interface as an administrator. Select "Configure Manually". Navigate to Support Settings >> Log Level Settings. Click the gear icon to edit. Remove any unnecessary log components. Remove any components with a "DEBUG" or "TRACE" level, unless actively troubleshooting an issue. Ensure, at a minimum, that an entry for "All - INFO" is added.