Operations | Monitoring | ITSM | DevOps | Cloud

This minor update has a one big new feature.

In the traditional automotive world, teams often work in silos: the cybersecurity experts lock down the ports, the quality assurance teams hunt for bugs, and the functional safety engineers track the ISO 26262 compliance. At Canonical, we believe this fragmented workflow causes friction rather than collaboration. You cannot have a safe vehicle that isn’t secure, and you cannot have a secure vehicle running on poor quality code. This friction results in a slow and rigid development process.

Canonical is pleased to share its latest research report, “The open source chain of trust.” Based on a survey of 500 DevOps professionals, the report highlights how organizations approach their open source software supply chains. While many companies are moving toward verifiable provenance and automated security workflows, internal misalignment and disjointed approaches remain serious challenges for most teams. Read the report.

Standardizing the fleet: automated updates for multi-site management There's a specific kind of update that Drupal agencies and enterprise teams dread: a security release in something the whole fleet runs on, the PHP runtime, the database engine, or a shared service, with a patched version available now and a deadline attached. For a team managing a single site, moving to the patched version is an afternoon of work.

Here’s how Megaport’s new certification gives customers more confidence in the security, availability, and reliability of our platform. Trust is built into infrastructure long before anyone notices it. It sits behind the login screen, inside the change process, across the controls that keep systems protected and services available. It shows up in the quiet, operational work that customers rarely see but rely on every day.

Somewhere in your environment, a patch is sitting in a queue because the last rollout broke something, and nobody wants to run it again. That is the exact failure mode good patch management software is supposed to prevent, and multiplied across a few hundred endpoints, it is exactly the kind of gap attackers look for.

Most IT teams know how to perform a hardware audit in theory. In practice, the process breaks down at the same point every time: the data. Devices in the registry no longer exist. Devices that exist have no owner on record. Lifecycle information is scattered across spreadsheets and vendor portals. A hardware audit that starts from fragmented records doesn't produce a reliable result. It produces a best guess.

How asset tags help track equipment, reduce losses, and improve asset management across your organization.

Modernization assessments move faster when the structure is already in place. Instead of recreating custom fields, interview questions, and assessment workflows for every customer, you can use a custom field template to standardize how data is collected from the start. This guide shows you how to create a reusable Tidal Accelerator custom field template using Node.js and the Tidal API, so your assessments are easier to repeat, compare, and scale. So you’re starting a modernization practice.

Many teams start with a simple approach to on-call coverage. One person carries the phone this week. Someone else covers next week. Vacation requests are handled through emails, chat messages, or spreadsheets. When someone is unavailable, everyone is expected to remember who is covering. This works for a small team until the first missed alert. Duty scheduling is the foundation of reliable alerting.