Pass CSA CCSK Exam in First Attempt Easily

Introduction

1. Introduction

Hello friends. So first of all I would like today thank you for subscribing this course and putting your valuable time, effort and energy in watching this video and subscribing this course. So let's see what is there in the introduction, what we all cover in this particular course. So just before starting this introduction, just would like today that okay, this is still also you can be seeing early access and I'll keep on adding material in this particular course because this is a very interesting and good topic to learn going forward and we see that the other changes on daily basis. So I'll keep on adding material to this. So in this before the first concept which is the understand cloud agreements and contracts, I have added section just to give a base about the cloud computing that okay, why cloud is there? What is cloud? Why this NIST there's a story behind that which is a concept which one needs to understand then detailed about all the characteristics and a shared responsibility model. Because in cloud if you don't understand the shared responsibility model, it is difficult for us to understand the different concepts. So again, the first would bathe understand cloud agreement and contracts. Why this is like we have chosen on the number one because that is where when you negotiate with your cloud provider, how to negotiate the contracts, what all terms would be there, what are the major factors artifacts in case of cloud? What is the importance of SLA in cloud? What all you should mention in the SLA when you send an SLR service level requirement to the cloud vendor. So all these things are covered in the first section and the second section is about Cloud Asset and Secure Configuration Management where you will go through that okay. What are the different challenges in case of Clouding discovering the assets like your Windows machines or your Linux machines or your network appliances and then the concept of DevOps and cloud. How to have a secure configuration management and cloud so that your assets are updated in the configuration management database as well. And section three is about protecting data from unauthorized accessory. You’ll study different deployment models and security concerns, how to do the media sanitization once you do the key management, jurisdiction and location issues, how to check for the various audit reports, we’ll have a demo for that as well. How you check the audit reports of Shandling incidents in the cloud is about section four where we'll check that okay, what should be there and a good incident response plan. How will you check in case there is a breach happens for the CSP or the cloud service provider or cloud vendor, what is their breach notification? Who will notify the Lord agencies first in case some breach happens? So that is covered over here. Then incident response losses and cloud and then in case there is some legal hold or some legal requirement, who will give the logs, what kind of support you get from CSP? So all those things are covered in section four then section five is also very important which is about the legal and compliance. We will discuss about the different legal issues from jurisdiction perspective and then from contextual perspective then we discover then we study the EDiscovery challenge in the cloud how to get the documents which are required by the law which are required by the courting case of some legal hearing then in the which regulations to follow in cloud. So all these things will be covering in the section five. So this is it friends in this introduction lecture. So thank you again. Thank you for watching this lecture meeting the next lecture.

Hide

Core Cloud Computing Concepts

1. What is Cloud Computing

Hello, friends. Welcome to this lecture on cloud computing. In the last lecture we study that why we should learn cloud computing. So similarly, it is very essential to understand what is cloud computing before we log into AWS or Azure. So it would be very helpful for you to deploy the infrastructure onto Azure once you understand that. I have a solid understanding that, okay, what actually the cloud computing is I forgot about Azure or AWS for a time. Just try to grasp the concept of cloud computing. So we'll start by the definition first. So there are a number of definitions, if you’ll search on to the Internet, which are trying to define the cloud computing. So there are many definitions today which tend to address cloud platform from the perspective of academics, architects, engineers or providers or consumers. But there should be one single definition which defines the cloud computing. We can say that, okay, this is it. Now I understand the cloud computing. So for a decade almost, the research was going on, and it was very difficult for one, for the organizations to define the cloud computing directory, what cloud is. So I would say the NIHD, after a very long research, they provided a definition, this long definition. So don't worry about this long definition. So just we'll go through it once only. And once we study all the different characteristics and all those things. Then again we'll come to this definition. And it would be very easy for you. Believe me. That so for this slide. So that you should know that. Okay. And yes. You created this definition and for us to move on to the next slide wherein we study that. Okay. How this long definition came into the picture. So it would be good if you can just go through it once with me. Cloud computing, you can say, is a model for enabling UB case convenient on demand network access to a shared pool of configurable computing resources like network service, storage, application, and services that can be rapidly provisioned and released with the minimal management effort of service wide interaction. This model is composed of five essential characteristics three service model and three deployment models. So we'll probably see what are the service models, deployment models in this lecture only. So let's study that, okay? How this definition came into picture, what kind of research was going on. So, really, before NASD, there was no clear definition. About 2007 eight, there was no clear definition, and organizations were working or trying to understand that, okay, what does cloud computing is? Because there were small vendors there in the market, and they were trying to capture market, and even customers were trying to reap the benefits of cloud. So there was one definition, in fact, which was created by NST, but it was still in draft until 2009.So before NIST, the scenario was totally different. Let me hear your story. Before NIST, there were small vendors within the market. They were trying to capture the market, even customers, they were trying to use the services of the cloud provider. And they were thinking that okay, they can deploy their info quickly and they can start running the business. But the kind of benefits customers were looking for incase of service providers, they were not getting that. And even it was not clear for the service providers as well. That okay. What kind of services they should provide. What kind of baselines they should have. Even they were not having the clear idea because different kind of enterprises. They were coming and trying to load then in front of the cloud. Even for the cloud users. Similarly. They were not having set baseline in front of them. That okay. I want to use AWS cloud or Azure cloud or let's say, Oracle cloud. Right. So in that case, what should I look for? How do I compare? What should I look for? Will my info will be good, so we’ll be able to deploy quickly. So it should not be like if Netflix and youkan say that one other online streaming organization is there. So Netflix is charged for the other organization and the other organization charged for the Netflix. So there should be a transparency in the billing. So all those things as an organization, they were looking before moving on to the cloud. So there was a lack of clear baseline for the customers as well. So you can see before Ni St came into picture, or they provided the definition, which we have seen in the last slide. So in that case, for the cloud vendors, you can say the less trust was there. They were not getting not able to attract good amount of customers. Customers were elected to use the cloud service because no baseline was there. Even they were thinking that okay, how they’ll be charged for different services? For the cloud service, they were having very less use case, because if the customers would not becoming, how you'll be having use cases or case studies to represent to the next customers. So enterprises, they were not very satisfied because the contracts were not clear when they were trying to use the cloud services. More expenditure, you can see no clear guidelines, no stringent SLAs or variation in the contracts, no baselines were there, right? So when NIST came into the picture and they provided those baselines or those five characteristics, so they provided actually five characteristics to make this bond better. So NIHD said that okay, if you are aloud service provider, just look on these five characteristics. If you can provide more than five, it would be very good. But if you pay concentration on those five characteristics and we'll come to those five characteristics in the next slide, you'll have a good business, you'll have increased trust, more business customers would be ready to experiment, and you'll behaving a huge case repository, right? You'll be able to run much more than you think if you provide these five characteristics or to your customers, right? So as a cloud service provider, they got that, okay, if we'll work on these five characteristics, we'll have resource pooling and broad network access and all those things, then we can provide a good service to our customers and earn good amount of money. See, from a service provider, any service provider, their main name is customer Satisfaction and the second is Money, which is the byproduct, right? So similarly, they got the clue that, okay, we'll be able to provide good services by adopting these five characteristics which NIST provided and we'll have a happy customers. So for customers, what is the main or for the enterprises, what is main goal? That they should be able to save money, have a good business, right? They should have internal happy customers and at the top level, sea level, they should be able to save money while deploying the in front of the cloud. So that motor was, you can say sold after Nist came into the picture earlier, they were all struggling and cloud vendors were not getting that kind of business. Users were not letting that kind of services. So after NIST, you can say the satisfied customers were there less expenditure, they were having a transparency in the billing. So one organization is not being charged for the other. So clear contracts and clear baselines for the enterprises. So just remember what we stated, that okay, for both to check or the baseline was to check for those five characteristics. Don't worry, we will dig into those five characteristics one by one so that you can have a solid understanding of cloud computing. So this is the definition. You can see a definition or a note which was provided by the scientist of NIST. So, by the way, if you're not worried about NIST, if you're not from a security background, NIST is National Institutes of Standard and Technology which works worldwide, is a body which works on the standardization of things, right? So they prepared a standard, you can say, for cloud computing as well. So just go into the Internet and study what is NIST National Institute of Standard and Technology so they have various standards, later to various technologies, later to the application security and all those things. So nasty scientists say that now they have a tool to determine, like I said, extend to which the information implementation technologies they are considering to meet the cloud characteristics and models. This is very important because by adopting an authentic cloud which will be providing those five characteristics, they are more likely to reap the benefits of cloud, right? I said that if they are having those five characteristics, they can have cost saving, energy savings, rapid deployment and customer employment. So that was the thing, like kind of a tool was being provided by the NIST for the customers as well as for the service providers. So let's move the next slide. What comprises of this cloud computing, right? Like I said, those five characteristics, service models and deployment models. So what are those five essential characteristics which CSP cloud service provider like AWS, SEO or GCP they need to have in their infra like on demand, self service, broad network access, resource pooling, rapid elasticity and managed service. So you can check for the utility like models onto the internet also what exactly it is, but these are the five essential characteristics still measured service. Similarly, if you are in a cloud customer, you need to look for these five characteristics still measured service. When you are looking or choosing for the cloud provider or a cloud vendor, you can check that okay? Whether it provides on demand, cell service, broad network access, resource cooling or a med service. So this is the baseline which you need to look for and you'll be able to run your business in a good way. Similarly, these are the different service model whether you want to use infrastructure as a service or platform as a service like you need a VM from a scratch and then you want to deploy an infrastructure platform, you may be requiring a database and software service like you are having a chat applications and the boxes there, right? Drop boxes there. So office 365 so different things are there depending on the service you want to choose. So there are different models, right? And different models will be having different responsibilities. Similarly, deployment model, whether you want to use only your private cloud or a public cloud or a hybrid cloud, you want to use both the public cloud and private cloud. So this is the main thing which is being used by the organization for the large enterprise. If you're a small organization, they are good to go with the public cloud. So we'll come to this indifferent lecture in detail as well. This is it friends in this lecture. Hope you really enjoyed this lecture. So thank you friends. Thank you for watching.

2. What are 5 Important Cloud Characteristics which you need to look For

Hello friends. Welcome to this lecture on cloud computing. And in this lecture we'll study what are the different cloud characteristics which one needs to look for. So in the previous lecture we had a glimpse of those five characteristics, but let's see in the detail all these five characteristics. So what are those five characteristics which one needs to look for in case of cloud computing. So remember friends, in next couple of sections we'll study all these five characteristics on demand, self service, broad network access, resource pooling, rapid elasticity and major service one by one and in detail with all the examples, right? But before we deep dive into all these characteristics one by one. So one thing which we need to understand or before moving further, right, that all these characteristics we need to look when, let's say we are a customer or an enterprise, if we have to choose the cloud computing in any case of any model, let's say any service provider like Amazon, Microsoft Azure or Google cloud platform. So we need to look for these five characteristics, whether, let's say if I'm going to choose AWS, whether I'll be getting on demand cell service, is there a broad network access, repetitive or a major service, right? So in that case, I should choose that service provider which can give me maximum capabilities. So in that case I have a checklist as an organization, as a cloud customer, that okay, these are the things which I should look for as a baseline while choosing a cloud service provider. Similarly, in the case of if you are a vendor or a cloud service provider, you need to look for that okay, whether I am providing all these services like on demand, self service, broad network access, source pooling, rapid elasticity and major service to my customers. In that case, if I am providing all these services to customers or to the enterprises, I'll be able to get a huge amount of customers and by product is the money which I'll automatically be getting if the customers are having a trust in the cloud provider. So you can say that by cloud computing doesn't mean just supplementing those It resources, it actually means providing a strategy or core information technology to the users or to the enterprises. So these are the five essential characteristics you can say. Which are provided by the NIST. Which as a cloud customer or an organization you need to look for in case of CSP .Or if you are in a CSP. You need to look at OK. These are the characteristics which I should provide to my customers to have to earn money and to have a good trust within the customers. Now, since this is the model or the essential characteristics we need to look for in case of both the CSPs and in case of customer side. And just remember guys, this is a kind of a win win situation like we discussed in the previous lecture, so just let's take a different point of view, let's say from the developer point of view, right? So cloud computing, in this case for developers, it allows you to flexibly deliver integrated content and various applications. And in that case, you can get applications and services to any device anywhere, anytime. And you are getting a seamless scalable model and you are only paying for the resources which you will be using. Let's say you're using only for the infrastructure for the two applications. So you'll be able to get that there area number of tools available in case of different vendors, with the help of which you can have a really good integrated environment, right? And let's say from an It standpoint of view, cloud computing allows organizations really to free themselves from having procuring the hardware in advance, let's say when the spike will come or when that particular business will come, they can use the hardware. So it is like they need not to procure the hardware in advance. From a traditional It point of view, whenever, let's say, a business is coming, they can quickly go into the cloud infra and they can deploy their infrastructure. Now, that's similar in case of business point of view. So cloud computing enables providers to serve business almost of all sizes, from a multinational organization to a small sale organization, right? So if you'll talk about today, from an organization, from NASA to Netflix, they are using the cloud services and they are running their business very happy, very happily. So this is it, my dear friends, are pretty short lecture before we dig deep into each of the characteristics. Hope you have enjoyed the lecture. Thank you. Thank you very much.

3. On Demand Self service - 1st Characteristics

Hello friends. In this lecture we'll study the first characteristics of cloud computing which is on demand self service. So this is the first characteristics out of those five characteristics which we have had seen in the previous lecture. So let's see what is on demand self service? So on demand self service, if you just pay attention to the name, it is on demand self service, a kind of a service which you can provision yourself. So whenever there is a requirement, whenever there is a demand, so you can provision that particular service with yourself without anybody's interaction. So what does on demand self service says? And this definition is again provided by the NIST, because if you remember, this is one of the five essential characteristics and these characteristics were given by NIST. This definition is also given by NIST which says on demand self service is a feature, right? Allowing cloud computing users to manage their own virtual resources without interaction with the service provider. So let's say for an example, it is 03:00 A.m. In the midnight and I'm working for an organization and I need a 500GB of storage, right? So in that case, I should not be calling the service provider like AWS or Microsoft is your boss, just provide me this 500GB of hard disk drive, right? So on demand self service is whatever your requirement is. As different customers, they are having a different requirement. You should be able to get those service without the interaction of a service provider, right? I can log into the AWS console, you should be able to get those services. So let's see with the example. So if you'll see this company A, then company B, company C and company D, right? So each organization has a different kind of business, right? So organization A might be having a different kind of a business. They need more of computing resources or some messaging needs are there, right? Similarly, company C and company C users, they need application services only and company D, they need platform services or storage services only. So from this point you can just imagine that there are a number of organizations, right? Fortune 500 companies and all these organizations are there. So each and organizations, they're running different kind of business. Some are service based industry, some are engineering organizations. So some are doing research, some are stock based company, stock market organization, some are stock brokers. So each and every organization, they're having a different application needs, they need a different kind of infrastructure, they're having a different needs. So depending on your need, depending on your demand, right, whatever kind of resources you need should be able to get that. So this is the first characteristics which you should look for when you are choosing a service provider. That okay. Is there a provision that if I can go ahead and get those resources which I need at any point of time? So let's say if company A, they say that okay, give me ten virtual machines so I should be able to get that by doing self service or with the help of few clicks from the service provider. I should not be calling or sending an email to service Spider to give me ten virtual machines, right? So similar way, let's say if there is another need wherein says that give me 500GB of hard disk or give me two terabytes of hard disk drive. So in that case I should be able to get those details, all those services from the service provider without any kind of interruption. Now guys, remember this thing that on demand self service characteristics. Just think from both ways. If you are a cloud customer or a user of cloud services, how easy it would be to just log into the cloud console and get this 500GB of storage or ten virtual machines at the same time. Because in that case you'll not be waiting for someone to provision the resources for you. You have just provision the virtual machine hardest drive and you can install the application and run your business with no time. Now, think from a CSP point of view like in the last lecture we studied that okay, we need to study these five characteristics from both the standpoint of only then we'll have a solid understanding of cloud computing. So let's say you're a service provider and you are running different kinds of customers are using your cloud infra. In that case, you have automated the things in such a way that you're not responding to each and every request. You have automated the task that within the few clicks they should be able to get those resources. And in that case customers will have a great faith on you so that they can recommend the same to the other customers. So this is the best example of on demand self service.Other example apart from the cloud, if I say like ondemand self services, it is in a similar way like you log into the Amazon cloud and provision the resources. Like you go into the Amazon website and order your favorite books or your favorite shoes. Like it is an on demand self service.Whenever you need a book, you log into the Amazon console or Amazon portal and you ordered your book. So this is a self service. Again, that the example we are discussing is in the form of cloud services. So it is the same thing. So whenever there is a need, I can just log in and I can order for those services. So this is it in the first lecture which is about on demand self service first characteristics. Hoping hope you have enjoyed the lecture. So thank you guys. Thank you for watching. Meet you in the next lecture.

4. Broad Network Access - 2nd Characteristics

Hello friends. Welcome to this lecture on broad network access. So this is the second characteristic out of the five essential characteristics that we studied. So in the first lecture, we studied about the on-demand self-service. So in this lecture, we are coming to the second characteristic, which is broad network access. So let's study with the help of an example what it actually means and how it benefits both the cloud service provider and customers. So what is broad network access? Again, this definition is provided by the NIST and in very simple terms, which are easy to understand. So what does it say? That capabilities are available over the network and accessible through standard mechanisms that promote use by heterogeneous thin or thick client platforms, such as mobile phones, tablets, and laptops, right? So in that case, it should provide broad network access. What does it actually mean? Right, so see whether you are using AWS, SEO, or whatever type of cloud services or vendor, right? So NIST says as per these characteristics, the cloud platform, whether it is AWS, zero or cloud vendors platform, should be accessible over the different platforms. It should not be limited to the common devices such as laptops or workstations. But this also includes your mobile phones which we are using these days, your smartphones, thin clients and so on. So whatever the cloud platform is, it should be accessible through the different platforms, through the mobile. Also you should be able to manage your cloud platform similar way which we are able to manage our platform in case of traditional It as well, we are able to manage our infrastructure with the help of a laptop or a work station. You just need to log into your VPN or to the, what do you say, your Zen desktop and you are entering into the corporate network where you can manage your infrastructure in a similar way and is that you should look for broad network access. That whether the vendor has different types of access which they provide so that you can manage your infra through the different devices which are available apart from the traditional resources like laptops and a workstation. So just imagine these days that okay, if you are a cloud engineer or a cloud architect and you are just spending your holiday and you're just enjoying at the beach at the same time you got a request that okay, there is some critical thing which you need to manage. You can just open up your smartphone and you can log into your Amazon console or to the cloud console and you can manage your infrastructure. So really to provide all these things, cloud vendors are also working very hard or they are providing all these characteristics to the different customer. So again, remember that okay, we need to remember these characteristics from both sides because if as a customer I'm having the different options available with me to access my cloud resources, it is always better for me that okay, whichever devices I'm having handy available with me at any point of time, I should be able to manage my infrastructure like mobile phones, laptops and workstations. So think from the case of service providers as well. So in case of service providers, the more devices or the more you can say the type of network or mechanisms you provide to the customers so that they can manage the infra, you'll be having a variety of customers who are not restricted to laptops or workstations to come to you to get the services. In that case, the more mechanisms you have, you'll get more customers and more money in return. So from both ways, we need to look at how broad network access is helpful for the cloud service providers and the customers. So let's say if you want to, just for your help or for you to understand better. So let's say if you have an Amazon account or as, your client just go into the Google Store, right? So you'll see that onto the Google Store you'll find this AWS console. This is an app, you can open it up and with the same email ID, you can just open this app and you'll be able to manage your Amazon cloud with the help of this particular app and most of the services. So similarly, this Azure, Microsoft Azure is also having apps, alibaba Cloud or a Google Cloud, they're also having their apps through which you can log in and manage your infrastructure. So in this way, all the service wise they are providing, what they're doing is they're by providing all these mechanisms like providing those apps and all those services, they are providing a broad network access means they should provide various mechanisms to the customers so they can get the flexibility to log in and manage their cloud infrastructure. This is about the second characteristics. So this is it, my dear friends, in this lecture. So thank you, thank you for watching this lecture. We'll meet you in the next lecture.

Hide