Professional Cloud Security Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise has enabled Cloud Next Generation Firewall (Cloud NGFW) Enterprise with Intrusion Detection and Prevention Service (IDPS) in a global network firewall policy. A security engineer is investigating a potential command-and-control communication attempt targeting an internal Compute Engine workload. The engineer needs to query Cloud Logging to locate the Layer 7 threat detection record generated by the firewall endpoint and correlate it with the firewall policy rule execution.
Which query strategy and log structure should the security engineer use in Cloud Logging to analyze both events?
Query resource.type="http_load_balancer" with logName projects/.../logs/requests, filtering on jsonPayload.enforcedSecurityPolicy.outcome set to THREAT_DETECTED.
Query the resource type networksecurity.googleapis.com/FirewallEndpoint for logName networksecurity.googleapis.com/firewall_threat to inspect threat details, and correlate with firewall logs where jsonPayload.rule_details.action is set to APPLY_SECURITY_PROFILE_GROUP.
Query compute.googleapis.com/vpc_flows in Cloud Logging to view captured Layer 7 attack payload strings, and filter jsonPayload.reporter equal to FIREWALL_ENDPOINT.
Query cloudaudit.googleapis.com/data_access logs for the method name firewall.threats.detected, and join the result with project-level audit logs on the rule resource name.
Query resource.type="http_load_balancer" with logName projects/.../logs/requests, filtering on jsonPayload.enforcedSecurityPolicy.outcome set to THREAT_DETECTED.
Query the resource type networksecurity.googleapis.com/FirewallEndpoint for logName networksecurity.googleapis.com/firewall_threat to inspect threat details, and correlate with firewall logs where jsonPayload.rule_details.action is set to APPLY_SECURITY_PROFILE_GROUP.
Cloud Next Generation Firewall (Cloud NGFW) Enterprise provides advanced Layer 7 inspection powered by intrusion detection and prevention technologies. When traffic matches a firewall policy rule configured with the apply_security_profile_group action, Cloud NGFW evaluates the packet against defined threat prevention security profiles. Cloud NGFW generates distinct log streams in Cloud Logging: one for the initial firewall policy rule match and another for the deep packet Layer 7 inspection performed by the firewall endpoint.
networksecurity.googleapis.com/FirewallEndpoint and log name networksecurity.googleapis.com/firewall_threat. This record contains the threatDetails payload with critical telemetry including threat ID, severity, CVE references, and the applied action.jsonPayload.rule_details.action is logged as APPLY_SECURITY_PROFILE_GROUP. The engineer can cross-reference the connection 5-tuple (source IP, source port, destination IP, destination port, and protocol) between the firewall rule log and the threat log to pinpoint the exact connection and policy rule.category, threat_id, alert_severity, and direction (CLIENT_TO_SERVER or SERVER_TO_CLIENT).DROP), or generated alerts (ALERT).Querying the dedicated networksecurity.googleapis.com/firewall_threat log name combined with the APPLY_SECURITY_PROFILE_GROUP rule disposition is the only native mechanism in Google Cloud to perform end-to-end correlation between network firewall enforcement and Layer 7 intrusion signatures.
Query compute.googleapis.com/vpc_flows in Cloud Logging to view captured Layer 7 attack payload strings, and filter jsonPayload.reporter equal to FIREWALL_ENDPOINT.
Query cloudaudit.googleapis.com/data_access logs for the method name firewall.threats.detected, and join the result with project-level audit logs on the rule resource name.