Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A financial enterprise is implementing continuous configuration drift detection across its Google Cloud organization using Security Command Center. To mitigate risks highlighted in recent security bulletins concerning OpenSSH vulnerabilities, the security team needs to deploy a custom Security Health Analytics (SHA) detection module.
The module must evaluate all Compute Engine firewall rules across projects and automatically generate a CRITICAL finding whenever an active ingress rule allows unrestricted traffic from the public internet (0.0.0.0/0) to TCP port 22.
How should the custom SHA module and its Common Expression Language (CEL) expression be configured?
compute.googleapis.com/Firewall with enforcement set to audit to generate findings in Security Command Center.Organization Policies provide centralized, preventive guardrails across the Google Cloud resource hierarchy to restrict how resources are configured at deploy time.
enforce). They do not serve as custom detection modules within the Security Health Analytics detector.audit mode that registers custom findings in Security Health Analytics; detection of misconfigurations across existing assets requires Security Health Analytics modules or posture templates.CRITICAL), or finding categories in SCC.The requirement called for actively blocking developers from deploying firewall rules with open public SSH access at the resource manager level using preventive guardrails.
compute.googleapis.com/Instance, set the severity to CRITICAL, and define a CEL expression checking resource.data.tags.items.exists(tag, tag == 'allow-ssh').This option evaluates Compute Engine virtual machine instances (compute.googleapis.com/Instance) for the presence of a network tag named allow-ssh rather than inspecting actual network firewall rules.
default-allow-ssh). Checking an arbitrary tag string fails to detect all exposed instances.compute.googleapis.com/Firewall resources to detect if any active ingress firewall allows unrestricted 0.0.0.0/0 traffic to TCP port 22.allow-ssh without an underlying open firewall rule, or a firewall rule might expose port 22 to all VMs without requiring specific tags.The security policy specifically mandated auditing VM metadata tags rather than evaluating Google Cloud VPC firewall objects directly.
compute.googleapis.com/Firewall, set the severity to CRITICAL, and define a CEL expression that evaluates to true when an enabled ingress rule includes 0.0.0.0/0 in sourceRanges and allows TCP port 22.Security Health Analytics (SHA) custom modules allow organizations to extend Security Command Center's built-in vulnerability scanning by creating custom rules. These modules use Common Expression Language (CEL) to continuously evaluate asset configurations and metadata reported by Cloud Asset Inventory (CAI).
resource_types to compute.googleapis.com/Firewall instructs the SHA engine to evaluate all firewall assets within the organization or folder scope.predicate.expression must evaluate to true when a vulnerability or misconfiguration exists. When the condition evaluates to true, Security Command Center automatically creates an active finding.!resource.data.disabled), enforces incoming traffic (resource.data.direction == "INGRESS"), contains the public IP range (resource.data.sourceRanges.exists(r, r == "0.0.0.0/0")), and permits port 22 (resource.data.allowed.exists(a, a.IPProtocol == "tcp" && a.ports.exists(p, p == "22"))).severity: "CRITICAL" categorizes the finding appropriately in the Security Command Center dashboard and triggers corresponding alerts.compute.googleapis.com/Firewall, set the severity to CRITICAL, and define a CEL expression that evaluates to false when an ingress rule contains 0.0.0.0/0 and allows TCP port 22.This option configures the custom detection module with the assumption that the Common Expression Language (CEL) expression defines the desired compliant state (returning false on non-compliance to trigger an alert).
true.false when a firewall rule exposes port 22, Security Command Center treats the resource as clean and no finding will ever be generated for vulnerable rules.true = Resource violates policy / Misconfiguration detected $\rightarrow$ Create Findingfalse = Resource conforms to policy / No issue detected $\rightarrow$ No FindingThe engine followed standard Organization Policy boolean constraint logic where true signifies compliance rather than Security Health Analytics finding condition logic.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated