Dataflow shared responsibility

Security is a shared responsibility. Dataflow secures the scalable infrastructure that you use to run your Dataflow pipelines and provides you tools and security controls to protect your data, code, and models. While not an exhaustive list, this document lists the responsibilities for both Google and the customer.

Google's responsibilities

  • Protect the infrastructure: Google is responsible for providing secure infrastructure for its services, including physical security of data centers, network security, and application security.

  • Secure the platform: Google is responsible for securing its platform, including managing access controls, monitoring for security incidents, and responding to security events. Google also provides customers with tools to manage their own security settings and configurations.

  • Maintain compliance: Google maintains compliance with relevant data protection laws and regulations. Learn more about Google Cloud compliance.

  • Harden and patch images: Google hardens and patches the operating system of base images used by the Dataflow-owned images. Google promptly makes any patches to these images available. Security bulletins are provided for known vulnerabilities

Customer's responsibilities

  • Use and update your environment to the latest versions of Dataflow containers and VM images: Dataflow provides prebuilt containers and VM images to simplify the use of its services. Google will create new versions of these images when vulnerabilities are identified. It is your responsibility to monitor for security bulletins and update your environment promptly when new versions are available.

    You are responsible for ensuring that you properly configured your services to use the latest version, or to manually upgrade to the latest version. To use the latest VMs, restart long-running jobs by updating the job. For more information, see Upgrade and patch Dataflow VMs. To manage security issues responsively, it is recommended that you use custom container images.

    If you're using a custom container image or a custom template, you're responsible for scanning and patching the custom images to mitigate vulnerabilities.

    If you're using a Flex Template base image, to ensure security and reduce vulnerability risks, use Distroless base images when possible.

  • Manage access controls: You are responsible for managing access controls to your own data and services. This includes managing user access, authentication, and authorization controls, and securing your own applications and data. Learn more about Dataflow security and permissions.

  • Secure applications: You are responsible for securing your own applications running on Dataflow, including implementing secure coding practices and regularly testing for vulnerabilities.

    Learn more about Customer-managed encryption keys, networks and VPC Service Controls, and permissions best practices.

  • Monitor for security incidents: You are responsible for monitoring your own applications for security incidents, and reporting any incidents to Google as necessary.

What's next