Operations | Monitoring | ITSM | DevOps | Cloud

One update can brick everything

When hardware operates unattended in remote locations, a failed update could be an operational disaster. Bricking a device hundreds of miles away turns a simple software patch into a costly physical recovery mission. Without built-in self-healing mechanisms, one bad deployment can paralyze your entire field operation. Canonical offers solution.

NinjaOne's IT Horror Fest V: Careful What You Script For

Every IT pro has a wish list. Fewer tickets. Better documentation. One script that fixes everything. Join us for IT Horror Fest V on Oct 22 at 1pm ET to find out what network nightmares can be unleashed when those wishes come true. You'll hear true tales of downtime dread and production panic, then we'll reveal the fixes and guardrails that can save you from a similar fate. Also featuring: Ghoulish guests, phantasma-riffic prizes, an over-eager automation imp, and more!

Security Just Hit Machine Speed

What if we could eliminate vulnerabilities before they become a problem? Neil Watkins from Burns & McDonnell explains how AI, automated security assessments, and Harness CI/CD capabilities could transform vulnerability management. From reducing attack surfaces to rapidly responding to critical zero-day vulnerabilities, the future of security is about moving faster without slowing down developers.

The Upsun Performance Agent: a diagnosis instead of a call graph

The data to explain a slow endpoint is usually already sitting in your project. Blackfire has the profile. Continuous profiling has the flame graph. The traffic numbers show which route matters. The code is in git. What takes the afternoon is putting those four things next to each other and working out which function is responsible. That afternoon is what the Upsun Performance Agent is for.

How Upsun handled PHP2Shell: protection in place 22 hours before the patch

On 21 October 2026, the team behind PHP released an emergency fix for two critical security flaws. PHP is the programming language behind a large share of the web, including WordPress, Drupal and many online stores. Researchers at Wiz named the flaws PHP2Shell. An attacker could use them to take control of a website without ever logging in. Updating a website, its CMS, or its plugins doesn't help. The only real fix is (and was) a new version of PHP itself.

What Four Leadership Circles Revealed About Operationalizing DEX

Earlier this year, I spent time with technology leaders across four major cities – San Diego, Boston, London and Dallas, as part of four Leadership Circles. Taken together, the conversations reinforced how far digital employee experience has matured for many organizations. The focus has shifted from understanding why DEX matters to exploring what it takes to operationalize its success. San Diego focused on the changing role of IT and the strategic case for DEXOps.

Configure Your JFrog Curation Service

Learn how to configure the JFrog Curation service for the first time. This video walks through each setting on the Curation General page, including turning on Curation, connecting package types, compliant version selection and notifications, and explains what each one does. Creating Curation policies and advanced coverage are covered in separate videos. Read more about it in JFrog Docs.

Create a Legal Risk Policy in JFrog Curation

Protect your proprietary code with JFrog Curation! Learn how to create a legal risk policy that blocks packages with licenses you don’t want developers using. In this demo, we build a policy for the GNU AGPL license, add a waiver for a package covered by a commercial license, and configure how waiver requests are handled. Read more about it in the JFrog Docs.

Create an Operational Risk Policy in JFrog Curation

Protect your organization from the next software package hijacking with JFrog Curation! Learn how to create an operational risk policy in JFrog Curation that flags immature package versions. This walkthrough reviews the available operational risk conditions, explains why brand-new or outdated releases can carry supply chain risk, and shows how a Dry Run action lets you measure a policy's impact on developers before you switch it to Block.