This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC’s registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
Google plans to build out its Confidential Computing portfolio with the launch of Confidential GKE Nodes for Kubernetes workloads.
Google today announced new additions to its Confidential Computing portfolio as part of its Cloud Next OnAir event: Confidential Google Kubernetes Engine (GKE) in beta mode, and new features for Confidential VMs.
Confidential GKE Nodes is the second product in Google Cloud’s Confidential Computing lineup, following the July launch of Confidential VMs, which are generally available starting today.
Built on the same technology, Confidential GKE Nodes will give businesses more options for confidential workloads when they want to use Kubernetes clusters with GKE. Users will be able to configure a GKE cluster to only deploy nodes with Confidential VM capabilities, and they can keep data encrypted in memory with a node-specific key generated and managed by the AMD EPYC processor.
In addition to making Confidential VMs generally available, Google is announcing a few new capabilities added during the beta period. One of these is the inclusion of audit reports containing detailed logs about the integrity of the AMD Secure Processor Firmware responsible for key generation in Confidential VM instances.
Google is also adding new policy controls for Confidential Computing resources. Users can now use the IAM Org Policy to define access privileges for Confidential VMs; they may also disable non-Confidential VMs running in a project. More additions support this level of enforcement: Users can rely on a combination of policy constrains and firewall rules to make sure Confidential VMs only interact with other Confidential VMs, even if they VMs are in separate projects.
Read more details here.
Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
From DHS/US-CERT’s National Vulnerability Database
An issue was discovered on LG mobile devices with Android OS 10 software. The lguicc software (for the LG Universal Integrated Circuit Card) allows attackers to bypass intended access restrictions on property values. The LG ID is LVE-SMP-200020 (September 2020).
An issue was discovered on LG mobile devices with Android OS 8.0, 8.1, 9.0, and 10 software. BT manager allows attackers to bypass intended access restrictions on a certain mode. The LG ID is LVE-SMP-200021 (September 2020).
An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) (Exynos chipsets) software. The baseband component has a buffer overflow via an abnormal SETUP message, leading to execution of arbitrary code. The Samsung ID is SVE-2020-18098 (September 2020).
An issue was discovered on Samsung mobile devices with Q(10.0) (Exynos and MediaTek chipsets) software. Unauthenticated attackers can execute LTE/5G commands by sending a debugging command over USB. The Samsung ID is SVE-2020-16979 (September 2020).
An issue was discovered on LG mobile devices with Android OS 7.0, 7.1, 7.2, 8.0, and 8.1 software. Applications with sensitive security settings (such as the package verifier application) mishandle unknown-source installations. The LG ID is LVE-SMP-190002 (September 2020).