Blog on Logs

I am brainstorming security requirements for system logging. Can you think of others? Are some of these too lame to bother with? Do you know of specific attacks that might be relevant?

You can reply using an issue or email.

(Update Feb 21: This is documented by OWASP as Log Injection and by CWE as CWE-117. That documentation includes well-defined threat models).


Who should be able to read what? A confidentiality attack enables an unauthorized party to access sensitive information stored in logs.

  1. Logs contain PII of users. Attackers gather PII, then either release it or use it as a stepping stone for futher attacks on those users.
  2. Logs contain technical secrets such as passwords. Attackers use it as a stepping stone for deeper attacks.


Which information should be modifiable by whom?

  1. An attacker with read access to a log uses it to exfiltrate secrets.
  2. An attack leverages logs to connect with exploitable facets of logging platforms, such as sending in a payload over syslog in order to cause an out-of-bounds write.


What downtime is acceptable?

  1. An attacker floods log files in order to exhaust disk space available for non-logging facets of system functioning. For example, the same disk used for log files might be used for SQL storage of application data.
  2. An attacker floods log files in order to exhaust disk space available for further logging.
  3. An attacker uses one log entry to destroy other log entries.
  4. An attacker leverages poor performance of logging code to reduce application performance


Who is responsible for harm?

  1. An attacker prevent writes in order to cover their tracks.
  2. An attacker prevent damages the log in order to cover their tracks.
  3. An attacker causes the wrong identity to be logged in order to conceal the responsible party.

You'll only receive email when they publish something new.

More from Lucas Gonze
All posts