Hornetsecurity: Remote Management Survey Results

Hybrid and fully remote employees are officially mainstream and will definitely be a significant part of the employment landscape for the foreseeable future. The cybersecurity experts at Hornetsecurity wanted to learn more about how companies handle security when it comes to remote employees in 2022 and beyond.

To this effect, they conducted a survey among over 900 I.T. professionals from around the world, from various industries and company sizes, to find out more about their approach to remote management.

Here are the survey results highlights:

● 18% of I.T. professionals believe that remote employees are not working securely, and that company data is at risk. 

● According to 3 out of 4 I.T. professionals, employees are using personal devices to access sensitive company data. The majority of these cases are likely to be users accessing emails and documents on their personal mobile phones while using cloud-based systems office applications. 

● 1 in 3 organizations does not provide cybersecurity awareness training to remote employees. Considering that the main counter for the leading causes of cybersecurity issues is user training, the fact that 1 in 3 organizations does not provide said training to remote users is concerning.

● 1 in 6 organizations has suffered a cybersecurity incident directly related to remote working. 

If you want to learn more about the survey’s findings, you can find the full results and breakdown here.

Increase Kasten Catalog Storage

You may notice that Kasten indicated less than 50% on catalog storage. Less than 50% storage will not allow you to perform further Kasten upgrades. 

The first thing that you need to do is add more storage on the worker node & expand it.

If the problem still persists, then you need to increase the default catalog pv size from 20Gi to 40Gi.

Before you do that, you need to check and make sure your storage class allows you to do so.

Command:

kubectl get storageclass <storageclass> -o jsonpath={'.allowVolumeExpansion'}

Note:- take note of the dot inside the { }

The result must be "true"

Next steap

Run a helm upgrade to increase global.persistence.catalog.size to your desired value (example below sets to 40GB):

helm get values k10 --output yaml --namespace=kasten-io > k10_val.yaml && \
   helm upgrade k10 kasten/k10 --namespace=kasten-io -f k10_val.yaml \
   --set global.persistence.catalog.size=40Gi

You storageclass pv has increased to 40Gi

Kasten side: