
ACSC: Best Practices for Event Logging and Threat Detection
Aug 27, 2024
2 min read
The latest publication from the Australian Cyber Security Centre (ACSC) outlines essential strategies to enhance security through robust logging policies and advanced threat detection. By implementing these practices, organisations can significantly improve their ability to detect and respond to threats, safeguarding critical assets in a digital world. The guidance has been formed in collaboration with global cyber security agencies, including CISA and the NCSC (UK).
Why Event Logging Matters
Event logging is more than just a regulatory requirement; it is a foundational element of cybersecurity. It allows organisations to monitor network activities, detect anomalies, and respond to potential threats before they escalate into full-blown incidents. The guidance emphasises that a well-implemented event logging solution enables network defenders to make informed decisions, prioritise alerts, and support incident response by revealing the scope and extent of compromises.
Key Components of Effective Event Logging
Organisation-Approved Logging Policy: Developing a centralised and consistent logging policy is crucial. This policy should define what events need to be logged, how logs will be monitored, and the duration of log retention. It should also clarify the shared responsibilities between service providers and the organisation.
Event Log Quality: High-quality logs are essential for accurate threat detection. The guide stresses the importance of capturing detailed and relevant event logs that can distinguish between false positives and true security incidents. This is particularly important in identifying sophisticated threats like "Living Off the Land" (LOTL) techniques, where attackers use legitimate tools to conduct malicious activities.
Centralised Log Collection: Centralising logs enables efficient correlation and analysis, making it easier to detect patterns that may indicate a security breach. The publication recommends prioritising log sources based on their criticality, such as internet-facing services, identity management servers, and OT devices in industrial settings.
Secure Storage and Integrity: Logs must be securely stored and protected from unauthorised access, modification, or deletion. Implementing secure transport mechanisms, such as TLS 1.3, and ensuring log integrity through cryptographic methods are critical steps. Additionally, organisations should consider data redundancy practices to safeguard logs in case of system failures.
Detection Strategy for Relevant Threats: A robust detection strategy involves using behavioural analytics to spot anomalies that deviate from established baselines. The guide highlights the importance of detecting LOTL techniques, which often go unnoticed by traditional security measures. By establishing a baseline for normal activities and monitoring for deviations, organisations can better detect and respond to sophisticated attacks.
The full document is really worth a read and it can be found at the link below:
