July 30, 2026

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Google SecOps Marketplace Change Google Chronicle: Version 91.0

Updated Wiz Defend alert naming format in the following connector:

Google Chronicle - Chronicle Alerts Connector

Managed Service for Apache Spark Announcement New Managed Service for Apache Spark on Google Kubernetes Engine (formerly Dataproc on Google Kubernetes Engine) subminor image version:

3.5-dataproc-28

Key updates in this image version include:

Conda channels: The new 3.5-dataproc-28 subminor image version doesn't have preconfigured Conda channels, and is mapped to default aliases (such as 3.5 and latest).

Impact: When creating clusters with 3.5-dataproc-28 or using default aliases (3.5, latest), packages cannot be installed using Conda unless channels are manually configured during cluster initialization. Mitigation: If your workloads require preconfigured Conda channels, pin your clusters to the previous image versions before August 25, 2026. Default change schedule: All workloads must transition to image versions without preconfigured Conda channels after August 25, 2026 since the use of prior subminor versions with preconfigured Conda channels will be disallowed.

You may need to delete and replace existing clusters After August 25, 2026, existing clusters created with images that have preconfigured Conda channels (even if cluster jobs don't use Conda to install packages) need to be deleted and replaced with new clusters created or recreated with images that don't have preconfigured Conda channels. Virtual Private Cloud Feature General Availability: You can use the Resolve subnet mask …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://docs.cloud.google.com/release-notes#July_30_2026
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.