Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Logging and monitoring failures are a state in which unusual actions are neither recorded nor watched, so damage goes unnoticed. A log is a history of the use of a site and of its errors. The OWASP Top 10 (2021 edition) has an item on the same subject, named "Security Logging and Monitoring Failures". It refers to the failure to detect an ongoing breach, escalate it, and respond.
How do logging and monitoring failures work?
Consider a shop with no security cameras, or one that records footage but where nobody watches it. Even if there is shoplifting, you cannot tell when or what happened. You notice only after the shelf is empty.
OWASP gives examples of failures. Events that should be recorded, such as logins, failed logins and high-value transactions, are not recorded, and warnings and errors are logged inadequately. They also include not monitoring the records, and records staying only inside the device. Having no standard (threshold) for raising an alert, or no flow for who responds, is also a failure.
MITRE's CWE-778 describes the same problem as a weakness in which important events are not recorded or important details are missing. Points for a detailed check are on the logging and monitoring failures vulnerability page. A free consultation can go through whether your own site's logs exist and who reads them.
Why do logging and monitoring failures matter?
OWASP explains that without recording and monitoring, you cannot detect a breach. It is not a measure that prevents the damage itself, but it decides whether you notice before the damage spreads.
IPA's "20 Articles for Safe Website Operation and Management" asks you to keep logs for each of the web application, the web server and the network devices, and to review them regularly. This is because they are an important source of information when investigating the cause of an incident or unauthorized access.
You need to be careful about what goes into the records. OWASP's logging guide says not to include passwords, access tokens, session identifiers, encryption keys, card information and the like in the records. Build both into the design: recording, and protecting what is recorded.
Related terms
- Audit log: a record of who did what, and when.
- SIEM: a mechanism that gathers the logs of many devices in one place and analyzes them.
- SOC: a monitoring department that watches for alerts around the clock.
Next step
Settle how long logs are kept and who reviews them, and write both down. The free URL check cannot see your logs; it shows only what a visitor can see of your public pages, so contact us for the log review itself.
Frequently asked questions
How long should logs be kept?
OWASP asks you to keep them for as long as is useful for an investigation. The exact period varies with the size of the site and the information it handles. First check the current retention period, and extend it if it is not enough.
What should be recorded in logs?
OWASP lists successful and failed logins, failed authorization checks, and failed input validation, among others. Do not leave secrets such as passwords and access tokens in the records.
Frequently asked questions
How long should logs be kept?
OWASP asks you to keep them for as long as is useful for an investigation. The exact period varies with the size of the site and the information it handles. First check the current retention period, and extend it if it is not enough.
What should be recorded in logs?
OWASP lists successful and failed logins, failed authorization checks, and failed input validation, among others. Do not leave secrets such as passwords and access tokens in the records.