Can you trust open source?
Linux security is evolving rapidly, with critical implications for enterprise environments. As operational complexity grows, so do the nuances of securing and managing Linux and open source at scale.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
The case for preview environments with production data
Before he joined Upsun, Andrew Kester spoiled the biggest sale of a client's year. He was one of two or three web developers at a creative agency that did branding, logos, print, and websites. A design boutique was about to run its annual trunk show, and the discounts and featured brands were meant to stay secret until the reveal on Tuesday at noon. The client asked for a preview. The preview reached production.
What's actually inside your SBOM (and why it matters)
An SBOM is more than a compliance checkbox. It's literally a bill of materials for your product: every software component that makes it into what you ship, plus the metadata that tells you whether it's safe to use. This video covers what that metadata actually does for you: An SBOM earns its keep when it shows you what's actually there, version to version, on a continual basis.
When an AI Agent Breaks the Law, Who's Responsible?
An AI agent was given one simple task: book a gym class when a slot became available. Instead, it discovered a vulnerability in the gym’s software, gained administrative access, deleted another user, and booked the slot anyway. Australian AI technologist Andrew Bird had connected an AI agent to WhatsApp to automate a routine gym booking. But when the agent encountered an API without proper authorization checks, it didn’t simply stop. It found a way around the problem and used the vulnerability to accomplish the task it had been given. And that creates a much bigger question.
Shipped: Self-serve your MCP server credentials
Enterprise agent platforms need a client ID and client secret in hand before they will connect to anything. An admin with the Modify MCP Settings permission can now issue that pair directly in Settings, connect the platform, and manage the credential lifecycle on whatever schedule your security policy requires. No support request, no wait.
Preparing SharePoint for Microsoft 365 Copilot: Archive the Stale Content Without Losing It
What Kantar and Dentsu archived before rolling out Copilot, what Microsoft 365 Archive hides from Copilot, and how to keep old content findable.
How Much SharePoint Data Hasn't Been Touched in Years? Report It in GB
Three ways to total the GB of SharePoint files not modified in 2, 3 or 5 years: Purview content search, a PnP PowerShell script and SharePoint Storage Explorer.
What to Know About AI Code-to-Merge Platforms
AI coding agents can generate pull requests at a pace your team has never seen. The bottleneck has shifted from writing code to everything that follows: reviewing, iterating, and merging. AI code-to-merge platforms are the category of tools built to manage that entire lifecycle, from the moment an agent starts working to the moment code lands in your main branch. This article walks through ten questions you should ask before committing to a platform.
PostgreSQL IDE + AI Assistant | dbForge Studio for PostgreSQL
Manage the full PostgreSQL database lifecycle from one AI-powered IDE. dbForge Studio for PostgreSQL brings together database design, development, and administration, as well as data management, analysis, reporting, and extensive automation. Additionally, the integrated AI Assistant generates, explains, optimizes, and troubleshoots SQL queries directly in the Studio. It supports on-premises PostgreSQL databases and related cloud services such as Supabase, Heroku, Amazon Redshift, and TimescaleDB.
Making Shared GPUs Even Safer with Kubex and HAMi-core
Table of Contents A few months ago, we introduced Kubex support for the KAI Scheduler to improve GPU sharing for production inference workloads. The basic model is simple: The KAI Scheduler handles placement and GPU sharing. Kubex continuously observes usage and adjusts those allocations as demand changes. KAI provides the scheduling foundation. It lets multiple workloads share a GPU while accounting for the amount of GPU each workload requests. Kubex then closes the loop.