쉐도잉 연습: Cybersecurity Architecture: Data Security - 영상으로 영어 말하기 배우기

4 .35 million.

9 .44 million.

83%.

What do those numbers have to do with data security?

I'll tell you in a minute.

Welcome back to the Cybersecurity Architecture series, where in the first few videos, we talked about principles, fundamentals, about the various domains of cybersecurity.

We covered identity and access.

We looked at the endpoint, the network, applications in the last video.

Today, we're going to talk about data security.

which is what these numbers have to do with.

So the first one, 4 .35 million?

Well, according to the Poneman Institute, that's the average cost of a data breach.

worldwide.

That's a lot of money.

Every time somebody breaks in, that's what it's costing the organization on average.

And by the way, that's taking out some of the really large numbers that might have skewed the average.

So this is the baseline that we're looking at.

$9 .44 million cost of a data breach in the U .S.

twice as much if you're in the US if you get hit with this.

And 83%, what does that have to do with anything?

That is the number of organizations that have been hit by more than one data breach.

So this is answering the question, why do we need to care about data security?

Now we're going to talk about in the rest of the video about some of these aspects, about governance, about discovery, about protection, compliance detection, response.

survey found we reduce the cost of a data breach for you.

So stay tuned for that.

First of all, we're going to cover governance and discovery.

So think of this as a data security ecosystem, we're going to fill this thing out.

These are the technologies that go into allowing us to secure our data.

First of all, we have to have some sort of governance plan.

This is our way of saying, this is what we want to do.

If I don't define where the finish line is, I can't expect people to end up there.

So first of all, we're going to have a policy, a data security policy.

And in that, we're going to spell out what kinds of things are sensitive and what kinds of things aren't.

We're going to spell out a classification criteria.

that says this is keys to the kingdom and this is the lunchroom menu.

Nobody needs to protect that.

We don't really care.

That sort of thing, we need to spell out that criteria.

We need to also spell out what kinds of protections go with those different levels of sensitivity.

So we may have confidential, unclassified.

We may have super confidential, super top secret, super duper top secret, whatever your classification scheme is.

But you need to spell out what those are.

We can't expect the users in our company to protect the data if we haven't spelled out what those guidelines are.

governance, policy, classification.

Build a catalog that tells us this is where the data is.

This is where the really sensitive stuff is.

And you want to know where that is all the time.

We're going to be updating that as well.

And then build a resilience plan.

that says, if we lose data, how do we recover?

So we'll talk a little more about that later as well.

So that's the first stage, is build the plan.

Then we're going to move into discovery.

Now I've said this is what I want to do to cover our data and protect it.

Now let's go find where the data is.

A couple of different places that we can look for data types.

Databases, that's where we expect.

That's going to be structured data in most cases.

That's where we're going to see a lot of the keys to the kingdom, but don't overlook this other area.

files, emails, spreadsheets, all kinds of other things that make up unstructured data.

We need to be able to discover sensitive content in unstructured data as well.

In other words, in places where we might not otherwise look.

We expect the keys to the kingdom to be in the very sensitive database, but what if somebody makes a copy of that?

What if somebody excerpts parts of it and emails it to someone?

Now we've got sensitive data flying around a lot of other places.

And I'd like to look on the network and see as this data is moving around as well.

And maybe discover when there are certain types of issues that we could be running into.

protection.

So DLP is a technology that's important, that allows us to discover this stuff in real time on various systems,

and as data is flowing across our networks.

Okay, now we've covered the why of data security.

These numbers down here should be sufficient motivation for you.

How do we do governance and discovery, some of the general technologies there.

Now let's talk about protection and compliance.

I figured out how I need to secure things and where the stuff is, now how am I going to actually protect it?

Well, encryption is a huge part of that.

That is, I scramble the data so that only I can read it and the bad guys can't.

And I need to be able to do that for data at rest, like sitting in a database for instance, or data at motion.

Data that's in motion could be moving from one user to another, could be on a web server, and then it's being served up over across the internet.

So there's, I wouldn't need to be able to keep the data secure all the time, at rest and in motion.

If I'm going to be encrypting data, the other thing I need to be able to do a really good job of is managing the keys.

If you lose the keys, you lose the data.

So remember that we want to generate keys in a random way.

If anyone can predict the way keys are generated, then all bets are off.

They can read all your data.

So it has to be done randomly and we need to be able to keep it.

We also need to be able to keep up with the lifecycle of a key.

That is, don't encrypt it once and forget it.

It's not encrypt and forget.

It's encrypt and then continuously follow the life cycle and re -encrypt at appropriate times.

We have keys that we rotate in and we rotate out.

Another aspect of all this that you need to be paying attention to is this notion of quantum safe crypto.

Quantum computers are going to be able to break all of our existing cryptography in the next number of years.

We don't know exactly when, but it's not that far off.

And so we're going to need to keep an eye on this space right here

so that we use new algorithms

that will keep our data safe against the quantum threat

that would be out there if someone had a quantum computer

and started trying to crack all of our data that we had previously secured.

100

Access control is another part of data security.

101

Access control is also part of identity and access management, which was the first of the seven domains that we covered.

102

But it relates here as well, because it doesn't matter how strong I've encrypted the information, if a user that has access to this,

103

set their password to the word password, then it doesn't matter because they're getting in.

104

If we don't have a good way of authenticating and authorizing users, then all of this strong crypto isn't going to matter.

105

So access controls need to be there.

106

Backup.

107

If we face in particular a disaster recovery scenario or a ransomware type scenario, where someone says, I've got your data and I'm not giving it back.

108

Well, the best defense against that is saying, guess what ransomware guy?

109

I've also got a copy of my data and I'll just restore it and you can go pound sand.

110

So this is the type of protection that we need, not only to keep the data from prying eyes,

111

but also keep the data so that we have a level of resilience that I mentioned earlier.

112

or disaster or things of that sort.

113

Also, I need to be able to ensure that I'm complying to some of the industry regulations that might exist.

114

The Generalized Data Protection Regulation in Europe, GDPR, we have in the US HIPAA for healthcare information.

115

There are lots of regulations in lots of industries in lots of parts of the world.

116

It's essentially, if you've got any information about somebody, there's a chance that you would be subject to one of these regulatory requirements.

117

So I need to be able to report.

118

on am I complying with that?

119

Just as much I need to be able to report when I'm not complying.

120

Because if I don't know that, then one of the costs that goes into these data breaches are the fines that go along with it.

121

And with GDPR in particular, it's very substantial.

122

And if you think because you're operating a company that's not in the in Europe, in the European Union, that you're exempt from this, think again.

123

If you've got European citizen data, even if you don't operate there, you could potentially be subject to that check with your lawyers to find out.

124

And then, a policy, I need an ability to retain records, but only as long as is necessary according to the law or other regulation.

125

It really doesn't do us good to keep a lot of information and just store everything forever.

126

So what we need to do though is the law will require that we store data for a certain period of time, and we want to store it for that long, and probably not longer, because it gets more expensive.

127

And the longer we're holding this data, the longer we're holding a burden that if in fact, we could be held liable.

128

So it's best not to have it in the first place if you don't really need it.

129

Okay, now we've covered the first bunch of security protections that are needed about governance, about discovery, and things of that sort.

130

Now we're going to take a look at two more.

131

Detection and response.

132

Security is about prevention, detection and response.

133

These first ones are mostly about the prevention.

134

This is about the detection and response.

135

Detection.

136

Now, what does that involve?

137

Well, I need to be able to monitor my systems and see how data is being used.

138

How is it moving around my organization?

139

Who's using it under what conditions?

140

And in fact, I also may want to use a technology called user behavior analytics

141

that will monitor users and the way that they're looking at the data.

142

If they're downloading normally a thousand files a day and suddenly they start downloading a million files in a day, then that could be suspicious.

143

starts having a lot of interest in that data, then that could be an issue.

144

If someone is doing something different than their peer group, then that could be an issue.

145

So that's what user behavior analytics is looking for, those kind of cases.

146

So we're trying to detect misuse and abuse of the data.

147

And ultimately, I'm going to generate alerts

148

that are going to go up to some console and someone then can go take an action on that.

149

And the action is our response part.

150

So one of the things I might do is open a case.

151

and then assign that case to someone, and then they begin an investigation.

152

We might guide all of those efforts with something called a dynamic playbook.

153

A dynamic playbook would tell you, this is what just happened, now you need to do the following steps.

154

And based upon the results of those steps, I'm going to specify other steps for you to follow.

155

So that's the dynamic nature of it, as opposed to just a hard coded script that someone follows.

156

This is more like a dynamic script that they can follow.

157

But it leads people through and allows them to automate the recovery and orchestration and automation of these problems.

158

What's the difference between those two?

159

In a perfect world, I'd automate all of my responses, but we don't live in a perfect world.

160

Because we see a lot of these things that are first of a kind, type of situations a first of a kind i can't automate

161

because i don't know what i should have done

162

because i've never seen it before orchestrate is what i have

163

to do in a lot of these cases where basically i'm looking for certain things

164

and i'm providing guidance

165

but like an orchestra the conductor of the orchestra is conducting who's going to come in

166

when do the trumpets come in when do the the saxophones come in this sort of thing they're going to

167

basically direct all of this.

168

And that's what we're going to do in our response.

169

So think about those things.

170

We're going to talk about these actually in more detail in our next two videos, where we're going to talk about security monitoring and security response.

171

Okay, now we've done a quick flyover view of data security.

172

We started off talking about governance, setting the plan and saying this is what we intend to do.

173

And if we don't have that right, we can't expect to do the other parts right.

174

Then we move into discovery, find out where all the data is that we need to apply those policies to.

175

Then we're going to put those protections in place.

176

Then we're going to check our compliance and see if in fact we're doing what we intended to do.

177

We're going to look for anomalies.

178

Then we're going to respond when we find those and feed that information back into our policy.

179

So the whole thing then becomes this ecosystem of data security, and it involves a lot of different technologies.

180

So that's in general how we want to do this.

181

Now what I told you is if you would stay to the end, I'm going to tell you the top five things and you can see them here already.

182

So no need for a drum roll.

183

But According to the cost of data breach survey, these were the top five things that reduced the cost of a data breach.

184

Number one, AI.

185

Using artificial intelligence was top on the list.

186

And in fact, we started using AI a good deal already in this detect phase.

187

You'll hear more about that in the future videos as we cover that in the next one.

188

But you can expect to see AI be infused in all of these different spaces.

189

So look for that moving forward.

190

DevSecOps, that was a big part of the discussion in the previous video on application security.

191

If you missed that, make sure you go back and check that out.

192

But that breaks down the walls between DevSec and ops organizations and put security in a shift left position.

193

Incident response.

194

We talked about that here.

195

That's this response capability, and it's going to be the subject of our video two videos from now.

196

So again, stay tuned for that.

197

Cryptography, we've talked about that here in this particular space.

198

And as I said, if you can't encrypt the data, you can't protect it.

199

And then ultimately, employee training.

200

Because at the end of the day, it's not all about the technology.

201

There's an end user.

202

And the user, the human, is almost always the weakest link in any security system. So don't.

203

Ignore this part.

204

If you do, it's at your own peril.

205

Okay, there we go.

206

Those are the top five things that you can do to reduce the cost of a data breach, to reduce the likelihood that it ever happens to you in the first place.

207

Make sure you have a good plan for doing all of these things.

208

All right, now in the next video we will cover monitoring and then the following video security response.

209

So make sure you stay tuned to check those out.

210

Like, subscribe and hit the notify button so you'll know and not miss any videos in the series.

📺 같은 채널

✨ 추천 영상

178 문장

Data Presentation, Step-by-Step | Google Data Analytics Certificate

University StudentsBusiness English+1

105 문장

AI Governance Explained: Ethical, Transparent & Accountable AI for the Future

University StudentsBusiness English+1

26 문장

ngày 26 tháng 5, 2026

University StudentsBusiness English+2

137 문장

NotPetya Attack

University StudentsBusiness English+1

41 문장

🚨 Most organizations don't fail ISO/IEC 27001 because they don't understand the standard...

University StudentsBusiness English+1

66 문장

What Is Cybersecurity?

University StudentsBusiness English+1

160 문장

Why the US is Losing the Infrastructure War

University StudentsBusiness English+2

689 문장

Database Sharding! Designing Data-Intensive Applications chapter 6

University StudentsBusiness English+1

537 문장

Understand Microsoft Entra ID | AZ-104 | Episode 2

University StudentsBusiness English+1

30 문장

Research Source Mastery: How to Find & Verify Credible Data (2026)

University StudentsBusiness English+1

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →

쉐도잉 연습: Cybersecurity Architecture: Data Security - 영상으로 영어 말하기 배우기

What is Event Driven Architecture (EDA)?

What Is Jev? The AI Model That Doesn't Generate Text

AI, Machine Learning, Deep Learning and Generative AI Explained

Spec-Driven Development: AI Assisted Coding Explained

AI Agents vs Business Rules: Which Should Make Decisions?

AI & Education: Generative AI & the Future of Critical Thinking

EDR vs. EPP vs. NGAV

MCP vs ADK: How Modern AI Agents Connect and Work Together

The 7 Skills You Need to Build AI Agents

How Smart Organizations Will Use AI: Jevons Paradox & Workforce Impact

What are AI Agents?

Cybersecurity Architecture: Five Principles to Follow (and One to Avoid)

Zero Trust Explained in 4 mins

Data Presentation, Step-by-Step | Google Data Analytics Certificate

AI Governance Explained: Ethical, Transparent & Accountable AI for the Future

ngày 26 tháng 5, 2026

NotPetya Attack

🚨 Most organizations don't fail ISO/IEC 27001 because they don't understand the standard...

What Is Cybersecurity?

Why the US is Losing the Infrastructure War

Database Sharding! Designing Data-Intensive Applications chapter 6

Understand Microsoft Entra ID | AZ-104 | Episode 2

Research Source Mastery: How to Find & Verify Credible Data (2026)

이 수업에 대하여

핵심 어휘 및 구문

연습 팁

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법