What is the first step to enable Company A analysts to work in Google SecOps with data isolation and reuse of playbooks?

• A. Acquire a second Google SecOps SOAR tenant for Company A
• B. Provision a new service account for Company A
• C. Define a new SOC role for Company A
• D. Create a Google SecOps SOAR environment for Company A

Answer: (C)

Defining a dedicated SOC role for Company A establishes the necessary permission framework to keep data isolated while allowing playbooks to be reused across the Company A analysts. A role in Google SecOps controls who can access which data and what actions they can perform. By creating a Company A-specific role, you ensure analysts only see Company A’s data and can run the same set of playbooks, enabling consistent automation and collaboration without exposing other companies’ information. This approach provides proper isolation at the access level and supports reuse of automation content, which is exactly what’s needed to get analysts started efficiently.

Other options would introduce heavier architectural changes or rely on identity controls alone without enforcing data boundaries or preserving reuse. A separate tenant isolates data but adds complexity and overhead; a new service account handles identity but not data scope; a new environment can isolate but isn’t the most direct way to define who can see and reuse what.