SECURITY-OPERATIONS-ENGINEER practice question 7 of 15

Your organization has mission-critical production Compute Engine VMs that you monitor daily. While performing a UDM search in Google Security…

Full set: 60 questions

Domain Managing operations within a cloud solution environment

Your organization has mission-critical production Compute Engine VMs that you monitor daily. While performing a UDM search in Google Security Operations (SecOps), you discover several outbound network connections from one of the production VMs to an unfamiliar external IP address occurring over the last 48 hours. You need to use Google SecOps to quickly gather more context and assess the reputation of the external IP address. What should you do?
Answer options
A: Search for the external IP address in the Alerts & IoCs page in Google SecOps. Correct answer
B: Perform a UDM search to identify the specific user account that was logged into the production VM when the connections occurred.
C: Examine the Google SecOps Asset view details for the production VM.
D: Create a new detection rule to alert on future traffic from the external IP address.
Correct Answer:
A. Search for the external IP address in the Alerts & IoCs page in Google SecOps.
Explanation

The most efficient method to quickly assess the reputation of an external IP address within Google Security Operations is to use the "Alerts & IoCs" page. This feature integrates threat intelligence data, such as VirusTotal reputation scores and sightings from other security sources. By searching for the IP address as an Indicator of Compromise (IoC), you can immediately access aggregated intelligence to determine if it is a known malicious entity. This directly addresses the need to gather context and assess reputation, which is the primary goal of the investigation at this stage.

Why Incorrect

B. A UDM search for the user provides internal context about who was active, but it does not directly provide reputation data for the external IP address.
C. The Asset view focuses on the internal VM's properties, associated users, and recent events, not on the reputation of external entities it communicates with.
D. Creating a detection rule is a proactive response measure taken after an entity has been identified as malicious, not a method for initial assessment.

References

1. Google Cloud Documentation, Security Operations, "Investigate an IoC": The IoC Matches view is designed for this exact purpose. It "displays information about indicators of compromise (IoCs) found in your enterprise... It also provides enrichment from other sources, such as VirusTotal, and details about the prevalence of the IoC in your enterprise." This directly supports using this feature to assess an IP's reputation.

2. Google Cloud Documentation, Security Operations, "Investigate an asset": The Asset view "provides a comprehensive overview of an asset's current and historical state." Its focus is on the internal device, not the reputation of external IPs, making option C less direct for the stated goal.

3. Google Cloud Documentation, Security Operations, "How to use UDM Search": UDM Search is a powerful tool for querying raw log data. While it can find all events related to the IP, it does not inherently provide the aggregated reputation assessment that the IoC view does, making it a less efficient first step for reputation checking (Option B).

4. Google Cloud Documentation, Security Operations, "Rules and detections": This section explains that the detection engine is used to "create rules that identify threats." This is a forward-looking, preventative action, not an investigative step for assessing a past event (Option D).

Scroll to Top