Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

In the digital era, the ability to adopt and integrate technology quickly has become a key driver of business success. Technology decisions are increasingly being made outside IT organizations as cloud-based tools, SaaS platforms, and low-code/no-code solutions become more accessible. Known as business-led IT, this trend democratizes technology, empowering business leaders to innovate independently.

Many organizations today have strict data privacy regulations that they must comply with. These privacy regulations can often clash with the requirements of security, application and operations teams who need detailed log information. This how to guide walks you through redacting message fields for privacy purposes. At Graylog, many of the organizations who use our tool are logging sensitive data that may contain personally identifiable information, health related data or financial data.

In 2025, global cybersecurity trends like the rise of Zero Trust, tightening data privacy and AI regulations and growing concerns over cloud security will only accelerate. Each of these evolving forces will also shift paradigms for the privileged access management (PAM) programs charged with safeguarding IT, cloud ops and third-party vendor users as they perform high-risk operations.

Ivanti has disclosed vulnerabilities affecting Ivanti Connect Secure (ICS), Ivanti Policy Secure (IPS) and Ivanti Neurons for Zero Trust Access (ZTA) Gateways. According to Ivanti, CVE-2025-0282 has been exploited on a limited number of ICS appliances. There are no confirmed reports of exploitation for Ivanti Policy Secure or ZTA Gateways. There is no indication that CVE-2025-0283 is actively exploited or chained.

In my previous blog post, (OpenShift Virtualization Backup and Restore with Trilio in AWS ROSA Baremetal ) I discussed how to protect VMs running in OpenShift Virtualization, specifically in AWS ROSA Baremetal environments. In this post, I want to focus on how you can recover a VM in less than 3 minutes. When it comes to recovery in Kubernetes environments, many of us feel relatively at ease, especially if the Persistent Volumes (PVs) are not particularly large.