Skip to main content

Record exceptional events in logs


The system must register all exceptional and security events in logs.


The organization must properly record the exceptional and security events in duly protected logs (confidentiality), considering that an event of this type should not show confidential or detailed information of the problem in error messages to prevent the use of that information by an attacker or malicious user.

Recorded events allow error pages to display simple generic messages, alerting end users that an error has occurred, with some option to contact support.

The details of how to address these problems should be kept securely stored in a previously defined log storage. When an event of this type is not properly recorded, a malicious behavior can be proven difficult to detect or a forensic analysis can be obstructed in case an attack is successful.


  1. Use a centralized logging mechanism that supports several levels of detail. Make sure all events related to successes and failures are recorded.

  2. Make sure that the logging level is properly configured for production environments. Enough information must be recorded to allow a system administrator to detect attacks, diagnose errors and recover from attacks. On the other hand, recording too much information can lead to the same problems (CWE-779).


Given the scenario that critical security information is not recorded, an attacker can perform an attack that will not leave a trace during a forensic analysis. Therefore, discovering the cause of the problem, or the origin of one or several attacks, can prove to be very difficult or impossible.


  • Layer: Application layer
  • Asset: Logs
  • Scope: Responsibility
  • Phase: Operation
  • Type of control: Procedure