Okay, let's take a look at the top nine. The Notorious nine as faras common threats to cloud computing get so the first
we have to talk about data breaches and data breaches revolve around the loss of confidentiality of our information and too many organizations. This is one of the greatest risks that they have to consider. So if we're looking at confidentiality of credit card numbers
Aah! Financial data, health care, information companies, sensitive information, intellectual property
these air huge, huge concerns to an organization. So we talk about the potential for a breach. We're looking at that information becoming disclosed inadvertently.
Huge problem. Now, the second issue that we think about his data loss. So where if you look at breaches affecting the confidentiality of data, data loss affects the integrity and the availability.
So maybe the dad has been modified in unauthorized fashion. Or maybe the data is just all of a sudden not available. Could come from denial of service attacks could come from
Ah, you know, a failure. The cloud service provider, some sort of lack of redundancy there. But the bottom line is, if our dad is not available, it's worthless to us.
now account or service hijackings. So any time we talk about in a hijack, it's always an impostor taking over. So we could have in a pasta and impostor ah, masquerading as a service as a legitimate service
where, as ah, user from the inside of the organization tries to connect, thinking
that they're providing credentials or they're acting in a manner that's complaint in security policy. But if there's a masquerading service or process for system or whatever that might be, obviously we've got a violation here. We also run the risk of other individuals. Masquerading is as legitimate users.
Maybe that that false credentials, maybe they've stolen session information but any sort of a man in the middle sniffing account hijacking those air always gonna lead to bigger problems. Usually they're gonna rate lead to data breaches, at the very least. But perhaps other,
uh, more fraudulent activities as well
are insecure interfaces and application programming interfaces. So interfaces and AP eyes These were provided to us five vendors. You know, you can certainly see these when we're providing a platform is a service. Ah, one of the things that we do with coatings. We try not to reinvent the wheel.
So if I can use existing AP eyes, existing code assisting libraries, whatever those might be, that saves me time.
The problem is, I need to make sure I've verified and tested the security of these elements before I would introduce them.
Ah distributed denial of service or regular denial of service attacks. Always a concern. Not specific. Just a cloud computing. But if I were to take a clouds ah CSP offline Cloud service provider off line through some form of denial service, whether it's technical
or making a physical
threat or just natural disaster, you know, it could take a facility offline. What type of backup in redundancy does our cloud service provider have in place?
You know, again, we can have a denial of service without any sort of malicious intent. If a building loses power, that would certainly count. So we need to make sure that we understand our service providers
infrastructure and the mechanisms they put in place for redundancy.
All right, malicious insiders from our company or the cloud service providers you know, many times we will get all of these security mechanisms to keep the bad guys out of our organization. However, if we're realistic, we have to understand that the greatest threat comes from within.
So within our organization, but certainly within the Cloud Service providers organization.
So how did they get their employees? Ah, what? How are they insured against any sort of compromise from the inside? You know, those are questions that we really need to find out. Abuse of Cloud service is, well, you know, honestly, um,
it's inherent wink weakness of any Internet service is that it's on the Internet, right? I mean, that's the greatest vulnerability of anything on the Internet is that it's on the Internet, which again is You know, um, the whole purpose of cloud computing is availability
so that can work both ways, right? It's like when we look at networking networking networking is designed to share well. If we're setting up a mechanism to share, sometimes that's the opposite of security. So in our rush to make things available for work user's home users, however, that might be
we need to make sure that we still
take into consideration all the risks that we have to look at when associating information across the Internet.
All right. Insufficient due diligence and do care. You know, um, we have to be very careful with making sure we understand the big picture. And any time a technology or an approach comes about very quickly
and it may seem it does to me that that cloud,
um, the cloud structure infrastructure designs there for a long time. But it really seems to me that only after the last couple of years has there really been a push. Go to the cloud, go to the cloud. And any time we start moving towards something very quickly because we don't want to be left behind,
we have to make sure that we've done our due care in our due diligence.
So don't take these definitions back to law school with you. But due diligence means the research. I've made myself aware of the standards of the industry. I've looked at the threats that looked at the vulnerabilities. That's due diligence, then do care, says that with the proper policies and procedures in place,
and I've applied the appropriate control. So really, the two of them have to go together.
So essentially, what we want to make sure of is the organization that we're entrusting with our information has followed their due diligence and do care that they're doing the right things to protect the assets that we've entrusted with them and also that we've used to diligence and Duke here in shifting to the cloud.
All right, in the last bullet point shared technology. Any time you're sharing a host of facility resource is with another organization, that organization presents a threat to you,
right? And you think about multi tendency on a single cloud server. How many different PM's belonging to how many different organizations? So what happens? Give one organizations doing something illicit, and the entire hard drive is seized by the FBI?
Or if they're irresponsible with their security mechanisms,
can they have their portion, you know, their virtual machine compromised? Would it be something that, in the way could affect the host or other virtual machines on the system? You know, eyes their potential for data leakage across the V EMS. Those are all questions that we have to look at. So these notorious nine on
big considerations with cloud computing in general
now for different flat cloud port categories there other specific, you know, types of consideration. So, for instance, for infrastructures, a server, a service, what we're mostly concerned about his weaknesses on the PM's right. Any type of virtual machine attack
er tops a little bit about VM escaping and being able to move from one of'em to another.
The virtual networks and virtual switches themselves many times. Those have inherent vulnerabilities root kit, SVM based root kits and malicious hyper visors. The hyper visors kind of that ultimate level that operates between the virtual machine
and the system as a whole. So if we get malware or something malicious in between,
you know, the VM and the hardware, we have real problems. Ah, a single point of access as well. We have to consider that, um, you know, a CZ where store as we're using surfaces from the cloud. What happens if we can no longer connect to our cloud provider
now platform as a service things that we're thinking about here, because again, what we're looking to do is have a good platform in which we can develop our software. Well, are we gonna have appropriate system and resource isolation where we're gonna have the amount that we need, you know, as far as resource is go.
But also, we're gonna have proper isolation from other processes and said,
user level permissions, Who else is gonna have access to our code? And is it going to be easy enough to make sure all of our developers have the pro appropriate access without anyone else? Having access is well,
and then protection against malware and software is vulnerable to a malware. So we have to make sure again, that's consideration.
And then last, we have software's a service. What we're really looking at their three big issues. Data segregation. So you know, again, I'm storing my data in the cloud I'm using. The application of the clown was storing my dad in the cloud. Is that truly isolated and protected for from other organizations that are doing the exact same thing
of what sort of policies are there around access to my data protection of the data and then Web applications? You know, Web applications have tremendous vulnerabilities, as a matter of fact, in this force later will be talking about a WASP and will become at the top 10 vulnerabilities
toe Web applications. So that's coming up shortly