Migrating workloads to public cloud environment opens up organizations to a slate of new, cloud-native attack vectors which did not exist in the world of premise-based data centers. In this new environment, workload security is defined by which users have access to your cloud environment, and what[...]
We’ve all seen this scene in some movie or TV show: a hacker sits in a shadowy room, busily typing on his keyboard. Suspenseful music plays in the background, the camera pans around him in a slow movement, and within the space of a few clicks – voilà! – our protagonist has broken into the[...]
A common concern of our customers using cloud platforms like AWS is the horror tales about a negligent (or uninformed) developer inadvertently exposing AWS API keys online, only for hackers to find those keys, penetrate the account and cause massive damage.
Let’s start with the tricky truth: the problem with stopping data breaches is not about detection. We’ve seen this time and time again at GlobalDots, where we partner with security providers and customers alike to consult and provide security solutions to the new and evolving threats in the cloud.
Moving to the cloud is all about agility and speed. But this agility and flexibility frequently come at the expense of security, leaving organizations, customers, and their data at risk. Moreover, as more and more organizations adopt multi-cloud and hybrid cloud strategies, this is adding[...]
In this blog post, we are going to deploy a simple Dockerized Node.js application on Kubernetes using Helm. Before we move to the actual deployment process, we will get a brief intro of Docker, Kubernetes and Helm in order to understand why are we using these technologies in the first place.
Pursuing the perfect end-user experience, cloud services are incredibly easy to spin up, and much harder to restrain. None of us wants to be responsible for downtime just when business is booming. We therefore overprovision and overspend, making cloud computing, storage and networking services[...]
