+V16.2 General Logging
---+V16.2.1 Verify that each log entry includes necessary metadata (such as when, where, who, what) that would …
---+V16.2.2 Verify that time sources for all logging components are synchronized, and that timestamps in …
---+V16.2.3 Verify that the application only stores or broadcasts logs to the files and services that are …
---+V16.2.4 Verify that logs can be read and correlated by the log processor that is in use, preferably by …
---+V16.2.5 Verify that when logging sensitive data, the application enforces logging based on the data's …

V16.2 General Logging

This section provides requirements to ensure that security logs are consistently structured and contain the expected metadata. The goal is to make logs machine-readable and analyzable across distributed systems and tools.

Naturally, security events often involve sensitive data. If such data is logged without consideration, the logs themselves become classified and therefore subject to encryption requirements, stricter retention policies, and potential disclosure during audits.

Therefore, it is critical to log only what is necessary and to treat log data with the same care as other sensitive assets.

The requirements below establish foundational requirements for logging metadata, synchronization, format, and control.

1. Pregled

Naslov Standard
V16.2.1 Verify that each log entry includes necessary metadata (such as when, where, who, what) that would …

Verify that each log entry includes necessary metadata (such as when, where, who, what) that would allow for a detailed investigation of the timeline when an event happens.

V16.2.2 Verify that time sources for all logging components are synchronized, and that timestamps in …

Verify that time sources for all logging components are synchronized, and that timestamps in security event metadata use UTC or include an explicit time zone offset. UTC is recommended to ensure consistency across distributed systems and to prevent confusion during daylight saving time transitions.

V16.2.3 Verify that the application only stores or broadcasts logs to the files and services that are …

Verify that the application only stores or broadcasts logs to the files and services that are documented in the log inventory.

V16.2.4 Verify that logs can be read and correlated by the log processor that is in use, preferably by …

Verify that logs can be read and correlated by the log processor that is in use, preferably by using a common logging format.

V16.2.5 Verify that when logging sensitive data, the application enforces logging based on the data's …

Verify that when logging sensitive data, the application enforces logging based on the data's protection level. For example, it may not be allowed to log certain data, such as credentials or payment details. Other data, such as session tokens, may only be logged by being hashed or masked, either in full or partially.

1.1 Reference

1.2 Utvrđeni zahtjevi

1.3 Povezani propisi

2. Utvrđeni zahtjevi

Zahtjevi
Izvor Zahtjev

3. Povezani propisi

Propisi
Izvor Regulativa
  • OWASP -

    EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative.

    DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen.