Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
An audit log is a record of who did what and when. It keeps actions such as logins, administrator operations, permission changes, and views of important data in a form you can look back on. When something happens to your site, this record is the first clue for tracing the cause.
How does an audit log work?
Compare it with the opening record of a safe. If the record shows when, and by whom, which safe was opened, you can investigate when the contents fall short. With no record, only suspicion remains.
OWASP's logging guide says each entry should hold four things: when, where, who, and what. When is the date and time. Where is the function or the server. Who is the user or the source of the traffic. What is the kind of event and its result.
It also names the actions to keep. They include changes to users and permissions, administrator operations, access to sensitive data, importing and exporting data, and file uploads. There are also things you must not record, such as passwords and payment card information. Logging and monitoring failures shows what goes wrong when records are thin.
Why does an audit log matter?
Because without records you can know neither the extent of the damage nor the cause. OWASP says that without logging and monitoring a breach cannot be detected. IPA also lists detecting unauthorized access and grasping the state of damage as the main purposes of keeping logs.
How the log is protected needs attention too. If records can be rewritten or erased, their value as evidence is gone. OWASP lists limiting access rights to logs, using an area dedicated to logs, moving them to read-only media after writing, and recording the viewing of logs itself. For important transactions it points to a form of record that allows only appending.
IPA's practice guide is about a factory with control systems, but it names as targets for logging the important systems feared as targets of unauthorized access and the systems that have a user authentication function. For your own site, start from the entrances where a takeover does the most damage, such as the admin screen and login screen.
The confidential-information isolation feature of our Cyber Shield Gate can record downloads of confidential files, and our two-factor authentication component comes with an audit log. It also helps when you investigate the cause of tampering.
What should you check about your own records?
- Is each administrator operation recorded, with when, where, who, and what?
- Does any log hold passwords or card numbers?
- Are logs copied to a separate place, and who can change them?
For help, contact us.
A small team can start modestly. Pick logins and administrator operations, make sure each entry carries the four items, copy the log somewhere else every week, and name one person who reads it. You can widen the list later, once the habit exists.
Related terms
- SIEM: a mechanism that gathers logs from many devices in one place for analysis
- SOC: a monitoring team that watches for alarms around the clock
Frequently asked questions
What should an audit log record?
OWASP lists successful and failed logins, changes of permissions, administrator operations, access to sensitive data, file uploads, and changes of settings. For each, keep the date and time, the place, the user, and the action.
May I leave passwords or card numbers in a log?
No. OWASP says not to record passwords, access keys, session identifiers, encryption keys, or payment card information in logs. Personal information needs handling such as removing it, masking it, or replacing it.
Why keep logs in a separate place?
So that a break-in does not erase the records along with everything else. IPA's case also says that logs saved only inside the system may be deleted during unauthorized access, so keeping them elsewhere is effective.
Next step
First check whether your site keeps a record of administrator operations. The free URL check shows only what is visible from outside. For what to record and how to store it, contact us. What thin records cost you is described in logging and monitoring failures.
Frequently asked questions
What should an audit log record?
OWASP lists successful and failed logins, changes of permissions, administrator operations, access to sensitive data, file uploads, and changes of settings. For each, keep the date and time, the place, the user, and the action.
May I leave passwords or card numbers in a log?
No. OWASP says not to record passwords, access keys, session identifiers, encryption keys, or payment card information in logs. Personal information needs handling such as removing it, masking it, or replacing it.
Why keep logs in a separate place?
So that a break-in does not erase the records along with everything else. IPA's case also says that logs saved only inside the system may be deleted during unauthorized access, so keeping them elsewhere is effective.