PROFESSIONAL-SECURITY-OPERATIONS-ENGINEER · Question #26
You work for a large international company that has several Compute Engine instances running in production. You need to configure monitoring and alerting for Compute Engine instances tagged with…
The correct answer is D. Use the PUBLIC_IP_ADDRESS Security Health Analytics (SHA) detector to identify Compute. The correct approach is to use the PUBLIC_IP_ADDRESS SHA detector, which already identifies Compute Engine instances with external IPs. You can then check for the compliance=pci tag on those instances to scope the findings. This leverages built-in SHA functionality instead of…
Question
You work for a large international company that has several Compute Engine instances running in production. You need to configure monitoring and alerting for Compute Engine instances tagged with compliance=pci that have an external IP address assigned. What should you do?
Options
- ACreate a custom Event Threat Detection module that alerts when a Compute Engine instance
- BDeploy the compute.vmExternalIpAccess organization policy constraint to prevent specific
- CCreate a custom Security Health Analytics (SHA) module. Configure the detection logic to scan
- DUse the PUBLIC_IP_ADDRESS Security Health Analytics (SHA) detector to identify Compute
How the community answered
(25 responses)- A12% (3)
- B4% (1)
- C4% (1)
- D80% (20)
Explanation
The correct approach is to use the PUBLIC_IP_ADDRESS SHA detector, which already identifies Compute Engine instances with external IPs. You can then check for the compliance=pci tag on those instances to scope the findings. This leverages built-in SHA functionality instead of creating custom modules, providing efficient monitoring and alerting for PCI-tagged instances with
Topics
Community Discussion
No community discussion yet for this question.