Operations | Monitoring | ITSM | DevOps | Cloud

Cybersecurity refers to the processes and technology used to protect information technology networks, data, people, servers, endpoint devices and other IT-related systems from cyberattacks. The need for this protection has never been greater. All organizations (in both private and public sectors) now exist in a threat landscape that allows attacks against their IT infrastructure.

In our previous post, we addressed the most common questions platform teams are asking as they prepare for the retirement of the NGINX Ingress Controller. With the March 2026 deadline fast approaching, this guide provides a hands-on, step-by-step walkthrough for migrating to the Kubernetes Gateway API using Calico Ingress Gateway. You will learn how to translate NGINX annotations into HTTPRoute rules, run both models side by side, and safely cut over live traffic.

Modern application security is struggling to keep up with AI-driven development and cloud-native scale, especially when security feels bolted onto CI/CD instead of built in. Harness SAST and SCA bring AI-powered application security testing natively into the Harness platform, reducing noise and alert fatigue. By identifying only vulnerabilities that are actually reachable in production code, teams get findings they can trust and act on faster.

We’re delighted to announce a strategic partnership between Kosli and TeamTopologies - a collaboration that brings together SDLC Governance automation with the world’s leading framework for organizing business and technology for fast flow of value.

We recently sat down with representatives from 42 companies to discuss a pivotal moment in Kubernetes networking: the NGINX Ingress retirement. With the March 2026 retirement of the NGINX Ingress Controller fast approaching, platform teams are now facing a hard deadline to modernize their ingress strategy.

CertBot assumes every server that needs a certificate should also know how to request one, validate domain ownership, handle renewals, and manage failures. This makes sense with a handful of servers. One server, one cert, done. But infrastructures grow. Now you’ve got web farms sharing wildcards, load balancers, mail servers, VPN appliances. The “every server for itself” model doesn’t scale and isn’t sustainable. Even the Let’s Encrypt community knows it.

SSL failures don’t usually break a site all at once. A certificate expires, a chain changes, or a browser update tightens rules, and users start seeing warnings before teams notice. By the time alerts fire, trust has already taken a hit. This post reviews SSL monitoring tools from an operational standpoint. How they detect upcoming expirations, validate certificate chains, and surface issues across environments and domains.

New Relic and Splunk are two prominent tools in the world of observability and monitoring, each serving distinct purposes. New Relic is used for Application Performance Monitoring (APM), offering a full-stack observability platform. It is important to note that New Relic is not a SIEM tool, its primary focus is performance monitoring. On the other hand, Splunk is used for log management, machine data analytics, and is widely utilized as a SIEM tool.