Stay organized with collections
Save and categorize content based on your preferences.
Access Control
Access to infrastructure (vendor access)
A limited group of qualified and trained Google Security Operations DevOps engineers have access to the production service environment for support and maintenance purposes. Access is named and granted by role (RBAC) on a need-to-know basis and subject to least-privileged principles. Access is governed by a policy that requires satisfying password complexity and 2FA. These are enforced by an Identity Provider (IdP) service.
Access to SaaS Application
Users of the Google SecOps cloud service are provisioned with a unique account and are required to change their initial password in accordance with password best practices. In addition, Google SecOps supports SAML integration to manage access via an external customer organizational IdP.
Google SecOps utilizes a customizable RBAC mechanism to support any required flexibility or strictness on access control and provides a default Master Admin account which belongs to the customer.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-13 UTC."],[[["Google Security Operations DevOps engineers have limited, role-based access to the production environment, enforced by password complexity and 2FA."],["Users of the Google SecOps cloud service get unique accounts with initial password requirements and SAML integration options for external IdP management."],["Google SecOps employs a customizable RBAC mechanism for access control, offering a default Master Admin account to the customer."]]],[]]
