PROFESSIONAL-SECURITY-OPERATIONS-ENGINEER · Question #24
Your Google Security Operations (SecOps) instance is generating a high volume of alerts related to an IP address that recently appeared in a threat intelligence feed. The IP address is flagged as a…
The correct answer is D. Add an exception in the detection rule to exclude matches originating from specific asset groups. The correct approach is to add an exception in the detection rule that excludes matches from the sandboxing and test environment asset groups. This prevents alert fatigue by suppressing non- production noise, while still maintaining full visibility and alerting if the same IOC…
Question
Your Google Security Operations (SecOps) instance is generating a high volume of alerts related to an IP address that recently appeared in a threat intelligence feed. The IP address is flagged as a known command and control (C2) server by multiple vendors. The IP address appears in repeated DNS queries originating from a sandboxing system and test environment used by your malware analysis team. You want to avoid alert fatigue while preserving visibility in the event that the IOC reappears in real production telemetry. What should you do?
Options
- ATemporarily disable the rule to avoid unnecessary alerts until the IOC expires in the threat feed.
- BAdd the IP address to a Google SecOps reference list, and configure the rule to suppress alerts
- CReduce the severity score in the rule configuration when the IOC match occurs in any internal IP
- DAdd an exception in the detection rule to exclude matches originating from specific asset groups.
How the community answered
(36 responses)- A6% (2)
- B11% (4)
- C3% (1)
- D81% (29)
Explanation
The correct approach is to add an exception in the detection rule that excludes matches from the sandboxing and test environment asset groups. This prevents alert fatigue by suppressing non- production noise, while still maintaining full visibility and alerting if the same IOC reappears in real production telemetry.
Topics
Community Discussion
No community discussion yet for this question.