212-82 · Question #136
TechTonic, a leading software solution provider, is incorporating stringent cybersecurity measures for their Windows-based server farm. Recently, it noticed a series of unauthorized activities…
The correct answer is A. Implement a centralized logging server and analyze logs using pattern-detection algorithms. To gain insightful and effective analysis of Windows logs for tracing intrusions, TechTonic should implement a centralized logging server and utilize pattern-detection algorithms.
Question
TechTonic, a leading software solution provider, is incorporating stringent cybersecurity measures for their Windows-based server farm. Recently, it noticed a series of unauthorized activities within its systems but could not trace back tot he origins. The company Intends to bolster Its monitoring capabilities by comprehensively analyzing Windows system logs. Which strategy should TechTonic prioritize to gain an insightful and effective analysis of its Windows logs, aiming to trace potential intrusions?
Options
- AImplement a centralized logging server and analyze logs using pattern-detection algorithms.
- BSet up monitoring only for Windows Event Log IDs commonly associated with security breaches.
- CRoutinely back up logs every week and conduct a monthly manual review to detect anomalies.
- DFocus solely on logs from critical servers, assuming other logs are less consequential.
How the community answered
(58 responses)- A78% (45)
- B12% (7)
- C3% (2)
- D7% (4)
Why each option
To gain insightful and effective analysis of Windows logs for tracing intrusions, TechTonic should implement a centralized logging server and utilize pattern-detection algorithms.
Implementing a centralized logging server consolidates logs from all Windows systems, enabling comprehensive correlation of events across the entire server farm, which is critical for tracing the origin and spread of an intrusion. Analyzing these aggregated logs using pattern-detection algorithms automates the identification of suspicious sequences, anomalies, or known malicious patterns that manual review would likely miss, providing highly insightful and effective intrusion detection.
Setting up monitoring only for commonly known security breach Event IDs creates blind spots, as sophisticated attackers often use less obvious events or combine multiple innocuous events to achieve their objectives.
Routinely backing up logs weekly and conducting a monthly manual review is too infrequent and inefficient for effective intrusion tracing, especially when dealing with a series of unauthorized activities that require timely analysis.
Focusing solely on logs from critical servers is a dangerous strategy, as attackers frequently compromise less critical systems as stepping stones to reach high-value targets, creating significant blind spots in the investigation.
Concept tested: Centralized log management, anomaly detection
Source: https://learn.microsoft.com/en-us/azure/sentinel/connect-windows-security-events
Topics
Community Discussion
No community discussion yet for this question.