SECURITY-OPERATIONS-ENGINEER practice question 1 of 15

Your organization has recently onboarded to Google Cloud with Security Command Center Enterprise (SCCE) and is now integrating it with your organization's SOC. You want to automate the response process within SCCE and integrate with the existing SOC ticketing system. You want to use the most efficient solution. How should you implement this functionality?

Full set: 60 questions

Domain Managing operations within a cloud solution environment

Answer options
A: Use the SCC notifications feed to send alerts to Pub/Sub. Ingest these feeds using the relevant SIEM connector.
B: Evaluate each event within the SCC console. Create a ticket for each finding in the ticketing system, and include the remediation steps.
C: Disable the generic posture finding playbook in Google Security Operations (SecOps) SOAR and enable the playbook for the ticketing system. Add a step in your Google SecOps SOAR playbook to generate a ticket based on the event type. Correct answer
D: Configure the SCC notifications feed to send alerts to a Cloud Storage bucket. Create a Dataflow job to read the new files, extract the relevant information, and send the information to the SOC ticketing system.
Correct Answer:
C. Disable the generic posture finding playbook in Google Security Operations (SecOps) SOAR and enable the playbook for the ticketing system. Add a step in your Google SecOps SOAR playbook to generate a ticket based on the event type.
Explanation

Security Command Center Enterprise (SCCE) includes Google Security Operations (SecOps) SOAR, a platform designed specifically for Security Orchestration, Automation, and Response. The most efficient and intended method for automating responses to SCC findings is to use SOAR playbooks. A playbook can be triggered by an SCC finding, and one of its automated steps can be to interact with a third-party ticketing system's API to create a ticket. This leverages the built-in, integrated capabilities of the SCCE platform for a streamlined, low-code automation workflow, directly addressing the need for an efficient, automated solution.

Why Incorrect

A. This approach introduces an unnecessary intermediate system (SIEM) for a task that Google SecOps SOAR can handle directly, making it less efficient than the integrated SOAR solution.
B. This describes a completely manual process, which contradicts the core requirement to automate the response and is inherently inefficient.
D. This proposes a complex, custom-coded solution using Cloud Storage and Dataflow. It is significantly less efficient to build and maintain compared to using the purpose-built SOAR functionality within SCCE.

References

1. Google Cloud Documentation, "Security Command Center tiers": This document confirms that the Enterprise tier includes the full Google Security Operations platform, which contains both SIEM and SOAR capabilities. Under the "Enterprise tier" section, it lists "Security orchestration, automation, and response (SOAR)" as a key feature. This supports the premise that SOAR is the available and intended tool.

2. Google Cloud Documentation, "Google SecOps SOAR overview": This document states, "Google SecOps SOAR enables security teams to respond to threats faster, with more accuracy and at scale... It provides playbooks to automate response procedures." This establishes playbooks as the primary mechanism for automation.

3. Google Cloud Documentation, "Integrations" (Google SecOps SOAR): This documentation details the extensive list of integrations available for Google SecOps SOAR, including numerous ticketing and case management systems like Jira, ServiceNow, and Zendesk. The "Case Management" category explicitly lists these integrations, confirming that a playbook step can directly create a ticket in an existing SOC system.

Scroll to Top