A network security monitoring (NSM) system triggers an automated alert indicating anomalous outbound TLS traffic from an enterprise host to an unrated external IP address. In what sequence should a network analyst execute the technical triage and mitigation workflow?
- 1Correlate NetFlow telemetry with SIEM log records to verify traffic volume and pinpoint the internal host IP address.
- 2Implement a temporary firewall rule to drop session traffic between the affected internal host and the external target IP address.
- 3Retrieve full packet capture (PCAP) files from the NSM sensor to analyze the TLS handshake and cipher suite attributes.
- 4Update inline NIPS rule definitions to automatically drop traffic matching the identified malicious payload indicators.
Answer
The correct operational sequence begins with correlating NetFlow and SIEM logs to confirm host identity, followed by deploying firewall containment rules to halt active connections. Next, packet capture analysis is performed on the sensor data, and finally, custom NIPS signature rules are updated to prevent recurrence.
The standard network security monitoring operational workflow dictates starting with alert validation via NetFlow/SIEM correlation to confirm affected assets, applying immediate firewall containment to stop exfiltration, conducting deep PCAP analysis to extract threat indicators, and updating inline NIPS signatures for long-term prevention.
Step-by-Step Solution
Key Concept
Network Security Monitoring Triage and Response Workflow
Estimated Time:2m 0s