Traditionally, when you deploy an application, you have the entire data center, the servers that you run, you’re responsible for all of it in the cloud model and cloud security, there’s a shared responsibility between you and the cloud provider.
In a shared responsibility model, you need to rethink Security on what your responsibility is and what cloud providers responsibilities. Let’s take part form as a service as an example. When you look at pairs, You’re Building applications.
Migrating data to the cloud and building applications running on the cloud security. So you are responsible for securing the applications, the workload and the data while the cloud provider is responsible for managing the security of the platform. So that it’s compliant, it’s secure from the perspective of network.
The platform on down in terms of managing the containers runtime and isolation so that you have your own space within the platform. Whereas if you are adopting and migrating workloads, the cloud and you are using infrastructure as a service.
Cloud Security Provider
In the cloud security provider. Manages hypervisor on down. If you are using virtual servers, or if you are using bad metal, then you can completely control everything on up from the operating system. The virtual servers that you’re on and the data you bring it on.
So it’s very important to understand the adoption model whether you’re consuming high as or pass or if you are consuming SAS Where the cloud provider, manages, all the applications and security of it and you worry about the data that you bring in and plan accordingly.
So that’s a very important thing because it’s part of understanding your responsibility in ultimately, managing the risk and compliance of the workloads on the data that you bring to Cloud security. Now, let’s talk about architecture when you build applications and my great applications and modernize your apps. Let’s start with data with all the risk.
That you deal with the kind of data matters is a confidential data. Is it public data or sensitive data? That may deal with private information? Consider, all those factors and make a secure design around what your data security architecture should be. Make sure you have data at rest encryption so that The data is always encrypted whether you use a database as a service Object Store as a service or other ways to store data like block storage encryption is for amateurs.
I think about Key Management is for professionals. So having more control of your keys, provide you the ability in the context of shared responsibility model that you own your data, you have complete control of your data. So, as you think about Key Management, make sure you have an approach.
Sensitive data
Think about, if you’re bringing confidential data, you want to bring your own Keys, may be sensitive data, you want to keep your own keys so that how much control of the keys? You have. And the Hardware security module in which the key processing, the encryption decryption operations happen, more control. You have more responsibilities that you can take on so encryption at data addressed.
Data in motion as it comes from services to data stores or applications. So that as you think about data coming out the way your request, an API request coming out the way data in motion. And the new world we need to start thinking about when the application is actually processing. The data there is going to be data in its memory. So, you can actually start to protect data using Hardware based Technologies where you can protect in-memory data as well.
Data protection
So that when it is in use and in memory by the applications, you can protect it. So take a holistic approach to data protection, addressed in Motion, in use with full control of your keys, it can be bring your own keys. Even better, push the boundary with keep your own keys.
The application that serves the data. It’s not only about which application needs to have access. Make sure the data access is on a only need by need basis. Do not open up your data services to the whole world, beat network access or everybody to access the data. Make sure you exactly know which applications need to access or which users need to access the data to run your Cloud applications.
Make sure there are no vulnerabilities in your application, so scan your applications. So have a knapsack Application security approach so that you can do Dynamic scanning or static scanning of your application before you deploy it into the production and in the cloud native environment, you’re deploying container images. So you can scan your images can scan it for vulnerabilities before you deploy and sit your policy. So that you only have secured images in production any time. And if there is any vulnerability in the new world, you don’t need to patch these system. You just spin up a new container. No, I’m off you go.
That’s the beauty of a cloud native approach that your security built-in in every step. So at a container level. And the applications that serves the business logic, you can start to protect it. Then when you look at the users coming in, you want to manage access in terms of who the user is and what from where they are coming from.
Your application
You need to make sure who the user is of which serve as it is based on the identity of those services or users. So you can May access control to your application or data and also from the perspective of network access, you want to make sure only authorized users can get in and if there are Intruders of there you can make sure you can set it up so that they are prevented from accessing.
What application and your data in the cloud security, be through web application firewall in network, access control or denial of service distributed, denial-of-service protection and had intelligence built into these Network protection as well. So both identity and network in essence, you’re protecting your data. You need to manage access your apps. And the workload on the data that you have deployed on the cloud security, you need to have a continuous security monitoring. So that you know at any point whether you’re compliant your father sees. You can watch out for threats that you need to manage having an approach and set of tools to manage security and compliance posture is very important. So gaining insights,
About your posture compliance. And threats. So, from your deployment environment, you can Garner information, it can be security events, audit logs, flow logs from Network, or system that can be fed in so that you can figure out what your posture and complains and threats are in that police important for you to gain Insight. You need to have actionable intelligence so that you can start to remediate. You may figure out there’s a vulnerability. I continue to make city of deployed is vulnerable so you can see respin the container.
Devops
You can remediate and spin up a new container, there may be a particular axis from a network that seems to be coming in from a suspicious Network IP address. So you can block that. So ability to gain visibility and in size, and having that insides and turn it into actionable intelligence, and remediate is very important. So, let’s talk about. Devops devops is about development and operation.
Traditionally, we think about, okay, there’s application team that is doing the design and architecture called building code and then you throw it over the wall for the Enterprise security team to secure it and manage it. That should be rethought, fundamentally is not just about deaf and abs, but cloud security need to be aforethought, not an afterthought. So it should become SEC. They have Ops approach to your the way you build manage and run your applications. So you need to embed security into the entire lifecycle. What we call shift left, not only manage security, but shift left through the entire process. You need to have a secure design of cloud security.
Ask your plan, has you design and say what kind of data I am? I going to put what level of classification? What kind of applications are my building? Is it container-based? Is it a workload that I migrating, take that into account and what Integrations you need to do so that you can plan it and architect it then as you build it Embassy Security as part of the process. So you have security aware applications. For example, you may want to encrypt data. If it is sensitive data, you may want to encrypt the data from your applications before even you store into a
This phone so secure build. And you managed security. As part of, Devops as you have secured, design and architecture. You pass on that and build secure applications and deploy and manage security in a continuous fashion. And then you have a closed loop. So that whatever you find, you may need to remediate or re-architect your application or Implement certain things as threats landscape evolve.