セキュリティは共有責任です。Dataflow は、Dataflow パイプラインの実行に使用するスケーラブルなインフラストラクチャを保護し、データ、コード、モデルを保護するツールとセキュリティ制御を提供します。すべてが網羅されたリストではありませんが、このドキュメントでは Google とお客様の両方の責任を列挙します。
Google の責任
インフラストラクチャの保護: Google は、データセンターの物理的セキュリティ、ネットワーク セキュリティ、アプリケーション セキュリティなど、サービスに安全なインフラストラクチャを提供する責任を担っています。
プラットフォームの保護: Google は、アクセス制御の管理、セキュリティ インシデントのモニタリング、セキュリティ イベントへの対応など、プラットフォームの保護を行います。Google は、お客様がセキュリティに関する独自の設定と構成を管理するためのツールも提供しています。
イメージの強化とパッチ適用: Google は、Dataflow 所有のイメージで使用されるベースイメージのオペレーティング システムを強化し、パッチを適用します。Google は、これらのイメージに対するパッチを速やかに使用可能にします。既知の脆弱性については、セキュリティに関する公開情報が提供されます。
お客様の責任
最新バージョンの Dataflow コンテナと VM イメージを使用して環境を更新する: Dataflow には、サービスの使用を簡素化するために、ビルド済みのコンテナと VM イメージが用意されています。脆弱性が特定された場合、Google はこうしたイメージの新しいバージョンを作成します。セキュリティに関する公開情報をモニタリングし、新しいバージョンが利用可能になった時点ですぐに環境を更新するのは、お客様の責任となります。
最新バージョンを使用するようにサービスを適切に構成すること、または最新バージョンに手動でアップグレードすることは、お客様の責任で行っていただきます。最新の VM を使用するには、ジョブを更新して、長時間実行ジョブを再起動します。詳細については、Dataflow VM のアップグレードとパッチの適用をご覧ください。セキュリティの問題を迅速に管理するには、カスタム コンテナ イメージを使用することをおすすめします。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[[["\u003cp\u003eSecurity within Dataflow is a shared responsibility between Google, which secures the infrastructure and platform, and the customer, who manages their own data and applications.\u003c/p\u003e\n"],["\u003cp\u003eGoogle ensures the security of its infrastructure, platform, compliance, and base images, while also providing tools for customers to manage their own security settings.\u003c/p\u003e\n"],["\u003cp\u003eCustomers are responsible for updating their environment to the latest versions of Dataflow containers and VM images, including managing custom images and using distroless base images where applicable.\u003c/p\u003e\n"],["\u003cp\u003eCustomers must manage access controls, secure their own applications, monitor for security incidents, and promptly report any vulnerabilities to Google.\u003c/p\u003e\n"],["\u003cp\u003eIt is important for customers to subscribe to Dataflow security bulletins, follow Dataflow release notes, follow Apache Beam release notes, and avoid the deprecated Monitoring agent option.\u003c/p\u003e\n"]]],[],null,["# Dataflow shared responsibility\n\nSecurity is a shared responsibility. Dataflow secures the scalable\ninfrastructure that you use to run your Dataflow pipelines and\nprovides you tools and security controls to protect your data, code, and models.\nWhile not an exhaustive list, this document lists the responsibilities for both\nGoogle and the customer.\n\nGoogle's responsibilities\n-------------------------\n\n- **Protect the infrastructure**: Google is responsible for providing secure\n infrastructure for its services, including physical security of data centers,\n network security, and application security.\n\n- **Secure the platform**: Google is responsible for securing its platform,\n including managing access controls, monitoring for security incidents, and\n responding to security events. Google also provides customers with tools to\n manage their own security settings and configurations.\n\n- **Maintain compliance** : Google maintains compliance with relevant data\n protection laws and regulations. Learn more about\n [Google Cloud compliance](/security/compliance).\n\n- **Harden and patch images** : Google hardens and patches the operating system\n of [base images](/software-supply-chain-security/docs/base-images) used by the\n Dataflow-owned images. Google promptly makes any patches to\n these images available.\n [Security bulletins](/dataflow/docs/security-bulletins) are provided\n for known vulnerabilities\n\nCustomer's responsibilities\n---------------------------\n\n- **Use and update your environment to the latest versions of\n Dataflow containers and VM images** :\n Dataflow provides prebuilt containers and VM images to simplify\n the use of its services. Google will create new versions of these images when\n vulnerabilities are identified. It is your responsibility to monitor for\n [security bulletins](/dataflow/docs/security-bulletins) and update your\n environment promptly when new versions are available.\n\n You are responsible for ensuring\n that you properly configured your services to use the latest version, or to\n manually upgrade to the latest version. To use the latest VMs, restart\n long-running jobs by\n [updating the job](/dataflow/docs/guides/updating-a-pipeline). For more\n information, see\n [Upgrade and patch Dataflow VMs](/dataflow/docs/concepts/security-and-permissions#upgrade-patch).\n To manage security issues responsively, it is recommended that you use\n custom container images.\n\n If you're using a\n [custom container image](/dataflow/docs/guides/using-custom-containers)\n or a\n [custom template](/dataflow/docs/guides/templates/creating-templates),\n you're responsible for scanning and patching the custom images to mitigate\n vulnerabilities.\n\n If you're using a\n [Flex Template base image](/dataflow/docs/reference/flex-templates-base-images),\n to ensure security and reduce vulnerability risks, use Distroless base images\n when possible.\n- **Manage access controls** : You are responsible for managing access\n controls to your own data and services. This includes managing user access,\n authentication, and authorization controls, and securing your own\n applications and data. Learn more about\n [Dataflow security and permissions](/dataflow/docs/concepts/security-and-permissions).\n\n- **Secure applications**: You are responsible for securing your own\n applications running on Dataflow, including\n implementing secure coding practices and regularly testing for\n vulnerabilities.\n\n Learn more about\n [Customer-managed encryption keys](/dataflow/docs/guides/customer-managed-encryption-keys),\n [networks and VPC Service Controls](/dataflow/docs/guides/specifying-networks),\n and [permissions best practices](/dataflow/docs/concepts/security-and-permissions#best-practices).\n- **Monitor for security incidents**: You are responsible for monitoring\n your own applications for security incidents, and reporting any\n incidents to Google as necessary.\n\n - Subscribe to the [Dataflow security bulletins](/dataflow/docs/security-bulletins).\n - Follow the [Dataflow release notes](/dataflow/docs/release-notes).\n - Follow the [Apache Beam release notes](/dataflow/docs/resources/release-notes-apache-beam).\n - Learn more about [Monitoring](/dataflow/docs/guides/using-cloud-monitoring) and [Audit logging](/dataflow/docs/audit-logging).\n\n | **Note:** When using the Monitoring agent, the `--experiments=enable_stackdriver_agent_metrics` option uses a deprecated container image that isn't maintained and might have unpatched vulnerabilities. We recommend that you don't use this option.\n\nWhat's next\n-----------\n\n- Learn more about [shared responsibilities on Google Cloud](/architecture/framework/security/shared-responsibility-shared-fate).\n- Learn about how to [protect your software supply chain](/software-supply-chain-security/docs/practices)."]]
