24 March 2020, 11:18
The coronavirus crisis is challenging everybody in different ways.
From a technical point of view, the sudden switch to remote working can be difficult for a lot of companies. A lot of employees and IT teams seem to be on the verge of a nervous breakdown due to connectivity, VPN and remote desktop issues.
For ML6, the technical impact has been extremely limited as long as our employees have a stable internet connection at home and the projects we are developing is done on Google Cloud or any other public cloud.
The main reason everything keeps working is the lack of a central VPN server since our internal applications and the managed Google services are protected by an Identity Aware Proxy.
Let’s dive in a bit of theory why this works and it is more secure than centrally managed VPN solutions.
In traditional security architecture, every employee who wants to access applications or other services on a corporate network needs to be on the internal network. If you are not close to a local network, you have to join the network using a VPN.
The VPN and various firewalls are the perimeters you have to pass to get access. As soon as you are on the internal network, certain applications are protected by another layer of security but often network drives/databases/servers are accessible from a technical point of view.
If a hacker can get through the firewall or connect to your internal network you might have a security breach.
Zero Trust is a security concept centered on the belief that organizations should not automatically trust anything inside or outside its perimeters.
Every call to an application or service on the network should be verified before granting access. This boils down to 2 questions. Do we grant the user access? And do we trust the device?
This concept enforces more fine-grained control on application level and at the same time reduces the number of perimeters to manage.
Firewalls and networking routing is still essential but the more difficult to scale VPN layer can be removed for a number of applications.
This ensures that you can work safely without the need for any VPN or remote desktop client. In this scenario, it’s a no-brainer to enable MFA, multi-factor authentication for every user. MFA, preferably using hardware keys, is another modern layer of security to avoid unauthorised access.
Google, with the BeyondCorp methodology, is a forerunner in zero trust architecture. Enabling zero trust security for web applications is straight forward using the managed Identify Aware Proxy service if your application runs on Google Cloud Platform.
First of all, you need to manage your users and devices using Cloud Identity, then follow the scenarios outlines in the Identity Aware Proxy documentation based on how your application has been deployed.
If you want to protect applications running on your on-premise network it’s required to setup a Cloud Interconnect or Cloud VPN to route traffic between the networks in a secure way. Compared to on-premise VPN solutions these services are easy to scale up and down and don’t require long-term license agreements.
If you are using AD, Active Directory, to manage your users it’s easy to provision these users in Cloud Identity using the Google Cloud Directory Sync service.
Check out the VPC Service Control service to reduce the risk of data exfiltration.
So let’s try to turn the coronavirus into a driver for innovation!
Check if zero trust security is a short-term or long-term solution to reduce the impact and costs of VPN on your organization.
We’ve added plenty of references to Google, open-source and other public cloud vendors zero trust solutions so happy reading and experimenting.
References about zero trust architecture
Zero trust on Google Cloud Platform
Zero trust @ public clouds & other open-source solutions
Articles made with materials from russianxnxx.