c66125093d
* Create rule S6413 * Add first draft * Extend highlighting * Rewrite recommended * Rewrite recommended * Update rules/S6413/recommended.adoc Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com> * Add missing dot * Add additional description * Add code GCP code examples * Add missing "gcp" tag Co-authored-by: hendrik-buchwald-sonarsource <hendrik-buchwald-sonarsource@users.noreply.github.com> Co-authored-by: Hendrik Buchwald <hendrik.buchwald@sonarsource.com> Co-authored-by: hendrik-buchwald-sonarsource <64110887+hendrik-buchwald-sonarsource@users.noreply.github.com> Co-authored-by: Loris S. <91723853+loris-s-sonarsource@users.noreply.github.com>
6 lines
673 B
Plaintext
6 lines
673 B
Plaintext
Defining a short log retention duration can reduce an organization's ability to backtrace the actions of malicious actors in case of a security incident.
|
||
|
||
Logging allows operational and security teams to get detailed and real-time feedback on an information system’s events. The logging coverage enables them to quickly react to events, ranging from the most benign bugs to the most impactful security incidents, such as intrusions.
|
||
|
||
Apart from security detection, logging capabilities also directly influence future digital forensic analyses. For example, detailed logging will allow investigators to establish a timeline of the actions perpetrated by an attacker.
|