The coronavirus pandemic is affecting companies of all sizes all over the world and significantly impact on how many service companies deliver their services. The recommendation for social distancing is driving many employers to direct their employees to work from home, which may represent a material deviation from how they perform their daily tasks. But compliance activities don’t have to be put on hold during these challenging times. Below you can read about some of the tools we use to achieve and retain compliance while being a completely remote company.
During RSA Conference 2020 KernelCare CEO, Igor Seletskiy, had a chance to share the best practices of enabling compliance with faster patch management. In this article you will find the takeaways from the speech.
Live patching is a way of updating a Linux kernel without interruption.
Because kernel updates don’t take effect until the system is rebooted, Linux kernel live patching is most commonly used to patch severe Linux kernel vulnerabilities without rebooting servers.
Aside from improved service continuity and uptime, organizations with large server fleets also use live patching to avoid the administrative overhead associated with the coordination and planning needed to reboot multiple systems.
This tutorial will show how to use Kpatch to change the behavior of a running Debian 10 kernel without stopping it, changing the contents of /proc/uptime (and the uptime command) so that the system’s reported uptime is 10 years greater.
KernelCare will be at this year’s RSA Conference 2020 USA, in San Francisco’s Moscone Center, from 24 to 28 February 2020. We look forward to seeing you at Booth #6279 in the North Expo.
This year’s session is titled:
“Enabling Compliance with Faster Patch Management”
Read the article based on the session.
Igor Seletskiy, KernelCare’s CEO, will be in Moscone South on Thursday, February 27, 11:00–11:20, where he’ll discuss how KernelCare helps organizations with their compliance needs.
But there are many other great sessions to see. Here’s a short list of those that have piqued our interest.
At the end of January 2020, another speculative execution vulnerability was found in Intel processors. Any modern Intel CPU built before October 2018 is likely vulnerable to a discovered hardware issue that could allow attackers to leak sensitive data from the OS kernel, co-resident virtual machines, and even from Intel's secured SGX enclave.
You want more—more protection for business-critical applications running on Linux, applications that depend on glibc and OpenSSL.
As with the kernel, vulnerabilities in glibc or OpenSSL can’t wait to be patched.
That’s why, last November, we announced KernelCare+, an enhanced variant of KernelCare, one that patches vulnerabilities in essential user space libraries in addition to those in the Linux kernel. And as with KernelCare’s Linux kernel live patching, KernelCare+ updates applications without affecting their operational state—no restarts, no reboots.
Our enterprise customers want more: more integration, more support, more control.
That’s why we’re thrilled to announce the launch of KernelCare Enterprise, a new member of the KernelCare family specially tailored for companies with 1000 servers or more.
Data breaches happen all the time for all sorts of reasons. The ones that make the news have three things in common:
- The data affects you and me, the public, everyday people.
- The data affects many of us, millions, even billions.
- The companies looking after the data are household names.
In this article we’re going to look at three famous companies each of which lost a lot of people’s data.
A global financial services company (name confidential) recently used KernelCare to resolve a difficult Linux kernel patching situation and achieve SOC2 compliance. Read our latest case study to learn how it did that:
