A Security Operations Center (SOC) analyst receives a high-priority alert from a Network Intrusion Detection System (NIDS) indicating anomalous outbound TCP traffic on port 443 with a mismatched Server Name Indication (SNI) header. In what order should the analyst execute the following triage and response steps to effectively investigate and mitigate the network threat?
- 1Review the NIDS alert metadata to establish the source IP, destination IP, and triggered signature details.
- 2Query NetFlow record telemetry to evaluate total session duration and traffic volume transferred between endpoints.
- 3Correlate network telemetry with endpoint detection logs to identify the specific host process driving the connection.
- 4Implement perimeter firewall block rules and isolate the affected endpoint from the internal network.
Answer
The correct sequence begins with examining the initial NIDS alert metadata, querying NetFlow data to measure session impact, correlating network events with host endpoint logs, and ending with executing containment and network block rules.
The analyst must follow standard network security monitoring procedure: start by reviewing NIDS metadata for baseline context, examine NetFlow records for session metrics, cross-reference endpoint logs to determine the initiating process, and finally enforce containment once malicious activity is confirmed.
Step-by-Step Solution
Key Concept
Network Security Monitoring Triage Workflow
Estimated Time:1m 30s