Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Cloud logging and monitoring is the record of who did what in the cloud, together with the means of watching it. A log is a record of operations and events, and monitoring is the work of reading those records to notice anything abnormal. NIST SP 800-92 is written as a guide for organizations to understand why log management matters, and to build and maintain log management that can actually be used.
How does cloud logging and monitoring work?
It is like keeping camera footage and an entry register at a location outside the building as well. After something happens, you can trace who entered where and when. In the cloud, operations in the admin console, permission changes and access to data can all be recorded.
According to the OWASP Logging Cheat Sheet, logs also need protection from abuse such as tampering. For file logs it advises strict permissions, keeping them out of locations visible on the web, and lists ways to detect tampering. It also covers not writing sensitive values, such as passwords and payment card data, directly into logs.
The CISA #StopRansomware Guide advises storing and protecting logs from network devices, endpoints and cloud services. It says to enable logging on cloud resources and create alerts for abnormal use. It also touches on limiting which users can delete logs or change their configuration, as a matter of organizational policy.
Screen and feature names differ by provider. Points to watch for the service you use are summarized in the page on cloud logging weaknesses. Logs live inside your cloud account, which the free URL check cannot see, because it covers only the outside view.
Why do cloud logging and monitoring matter?
If an unauthorized login or a configuration change happens and nothing was recorded, you cannot trace afterward what occurred and when. The scope of damage cannot be fixed, and the response drags on.
Even when logs exist, nobody reading them means slow discovery. Arrange the records and the notification that flags abnormal activity as one pair.
Decide in advance how long to keep logs and who checks them. If a contractor operates the system, confirm in the contract whether you can read the logs yourself and how long they are kept.
Related terms
- Audit log: a record of who did what and when
- SIEM: a mechanism that gathers many records and finds abnormal activity
- Logging and monitoring failures: a state where records or watching are too thin to notice damage
- Least privilege: granting only the range that is needed
Frequently asked questions
How long should logs be kept?
Apart from cases fixed by law or contract, there is no single answer. Decide by thinking about how many days pass before wrongdoing is noticed and how far back an investigation must reach. Default retention differs by cloud provider, so check your own configuration.
I am worried that logs hold customers' personal data or passwords.
OWASP says not to record passwords, session identifiers or payment card data directly in logs. If something must be kept, decide how to handle it, for example by masking, summarizing or encrypting it.
Next step
The page on cloud logging weaknesses gives the order in which to review how records are kept. For help designing your logging, contact us.
Frequently asked questions
How long should logs be kept?
Apart from cases fixed by law or contract, there is no single answer. Decide by thinking about how many days pass before wrongdoing is noticed and how far back an investigation must reach. Default retention differs by cloud provider, so check your own configuration.
I am worried that logs hold customers' personal data or passwords.
OWASP says not to record passwords, session identifiers or payment card data directly in logs. If something must be kept, decide how to handle it, for example by masking, summarizing or encrypting it.