Like many of my peers, my role as a Chief Security Officer (CSO) has dramatically changed as we work to understand and adapt to COVID-19. It’s hard to believe that just a few weeks ago, my mind was focused on things such as FedRamp and the California Privacy Act (CCPA), now the majority of my time is focused on ensuring our employees safety and productivity, so they can continue to deliver products and support our customers and partners.

When I’m writing new software, one of the most important thoughts in my mind is how I’ll test to make sure it works. There are lots of ways to test software, and when you’re at your best, you should be using all of them. Sure, you should make sure that your QA team is able to verify that your code works before it goes live. You should make sure that the code passes acceptance tests, too.

Employee monitoring has become a standard practice across different industry verticals to examine productivity and ensure that company resources are being used in the right manner. In addition to keeping a track of the manner in which employees are working, it also allows preventing theft and serves as evidence in litigation. Employee monitoring applications offer a means of tracking the activities of employees and remove any guesswork about what employees are doing throughout the day.

Many business leaders are allowing workers to telecommute, to attract more Millennials and remain competitive in the labor market. And now, with coronavirus (COVID-19), becoming a remote organization is more than just a bottom-line decision. It can affect the health and welfare of a company’s employees. To address this new threat, organizations are now setting up remote workplaces, in days, if not hours.

Settling into any new job can be exhausting. New faces, new desk, new computer, new kitchen (and new kitchen rules), new… everything. On top of that, there are forms to fill in and return to multiple onboarding stakeholders, passwords to create, HR policies to read.

In 2019 multiple cities, hospitals and educational institutions in the U.S. were crippled by ransomware, including Baltimore, Atlanta, New York City, Regis University in Denver and Monroe University in New York. In the the last 12 months, the infosec community has seen these ransomware operators seriously upping their game (see Ryuk ransomware).

There are 1.3 billion websites out there in the great unknown and it’s hard not to think about what makes them different from one another. Why do users flock to one website and ignore the other completely? One major differentiator is, of course, content. I’m not going to dwell on what type of content is better. Another reason why users stick to one website over another is the user experience. Today we’ll be looking at a third major differentiator: Website Performance.

Longhorn is cloud-native distributed block storage for Kubernetes that is easy to deploy and upgrade, 100 percent open source and persistent. Longhorn’s built-in incremental snapshot and backup features keep volume data safe, while its intuitive UI makes scheduling backups of persistent volumes easy to manage. Using Longhorn, you get maximum granularity and control, and can easily create a disaster recovery volume in another Kubernetes cluster and fail over to it in the event of an emergency.

The global corporate landscape is on the brink of a complete premises lockdown in light of the COVID-19 crisis. Service disruption is inevitable, and enterprises’ business continuity plans are being put to the test. Despite this challenge, it’s heartening to see companies across nations take quick steps to ensure the health and safety of their employees during these trying times.

We’ve been working on something big. We’re building Request Metrics, a new service for web performance monitoring. TrackJS is a fantastic tool to understand web page errors, but what if your pages aren’t broken, just slow? What if the checkout page takes 10 seconds to load? What if that user API is slowing down from your recent database change? What pages have the worst user experience? Request Metrics will tell you that.