Operations | Monitoring | ITSM | DevOps | Cloud

The “hybrid fleet” is today’s reality: organizations diversify operating systems while Microsoft Active Directory (AD) remains the dominant identity “source of truth.” IT administrators must ensure Linux machines, like Ubuntu desktops and servers, behave as first-class citizens in this environment.

The way enterprises are thinking about their infrastructure has changed. Digital sovereignty of all kinds – data sovereignty, operational sovereignty, and software sovereignty – have begun to dominate the infrastructure discussion. Today, these abstract terms have become practical concerns for platform teams.

30 years after its introduction, Secure Shell (SSH) remains the ubiquitous gateway for administration, making it a primary target for brute force attacks and lateral movement within enterprise environments. For system administrators and security architects operating under the weight of regulatory frameworks like SOC2, HIPAA, and PCI-DSS, default SSH configurations are an “open door” that represents an unacceptable risk.

In the modern DevSecOps world, CISOs are constantly looking for signals in the noise, and the outputs of security scanners often carry a lot of weight. A security scan that returns a “zero CVE” report often unlocks promotion to production; a single red flag can block a release. This binary view of security has birthed two diametrically opposed philosophies. On one side, we have the long-term support (LTS) approach: stay on a battle-tested version and backport specific security fixes.

In September 2025, dozens of popular JavaScript packages, like chalk and debug, were compromised on the npm registry. These packages are so ubiquitous they end up in everything: front-end apps, back-end microservices, and CI tooling. Developers didn’t do anything wrong, they just ran the same command they always do: npm install chalk. But then the malware arrived silently. This wasn’t a bug in an operating system. It wasn’t a virus on someone’s laptop.

Today, we’re excited to introduce the beta release of MicroCloud Cluster Manager, a new way to discover, organize, and operate your MicroCloud environments from a single, unified interface. MicroCloud is an open source cloud platform that makes it simple to create lightweight, resilient clusters anywhere. As teams scale from one cluster to many, visibility and coordination quickly become essential. Cluster Manager is built to solve exactly that.

Canonical is working with Microsoft Defender to improve the security of organizations’ mission-critical Linux workloads.

Teams continuously deploy programmable telemetry pipelines to production, without having access to a dry-run mode. At the same time, most organizations lack staging environments that resemble production – especially with regards to observability and other platform-level services.

As AI platforms grow in scale, many of the limiting factors are no longer related to model design or algorithmic performance, but to the operation of the underlying infrastructure. GPU accelerators are key components and are responsible for a large part of the total system cost, which makes their continuous availability and stable operation critical to the output and efficiency of the entire AI platform.

Increasingly, enterprises are interested in improving their level of control over their data, achieving digital sovereignty, and even building their own sovereign cloud. However, this means moving beyond thinking about just where your data is stored to thinking about the entire data lifecycle. In this blog, we cover the differences between data residency and data sovereignty, how confidential computing works to enhance the security of your data, and can support you in achieving digital sovereignty.