As our enterprise customers build out large, multi-cluster Kubernetes environments, they are encountering an entirely new set of security challenges, requiring solutions that operate at scale and can be deployed both on-premises and across multiple clouds.
Working from home has become our new normal, with many of our jobs being performed remotely. The experience of working remotely can be as seamless as it was from our workplace, with all the technological advancements available today. Businesses have also put network security on the forefront by implementing use of virtual private networks (VPNs). This enables users to securely access confidential information hosted on the organizations’ servers.
The Health Insurance Portability and Accountability Act, also known as HIPAA, is a compliance standard that was implemented after all health-related information was digitized. The crux of the act is to ensure that all sensitive electronic protected health information (ePHI) has restricted, secure access. Various aspects of your network determine your compliance with HIPAA standards. Let’s discuss some of these important components in detail.
In our previous post on API Gateways we discussed how services handle external client to service(North-South) traffic. When it comes to dealing with service to service(East-West) traffic it is common to implement a Service Mesh.
