쉐도잉 연습: Cybersecurity Architecture: Five Principles to Follow (and One to Avoid) - 영상으로 영어 말하기 배우기

With the rise of cyber attacks and data breaches, it's never been more important to make sure that your organization is protected against hackers.

This series is about cybersecurity architecture, and we're going to talk about two different areas: fundamentals, where we're going to go through

and discover what some of the principles of cybersecurity are that need to be applied to everything that you do.

And then the second part is on various cybersecurity domains.

Here, we're going to explore how to identify vulnerabilities implement best practices,

and defend against a wide range of cyber threats through an all -encompassing cybersecurity architecture.

By the way, I'm an adjunct professor at NC State University, and there I teach a 400 level course on enterprise security architecture.

This video series is based upon that course.

The bad news is you won't get college credit for watching these videos.

The good news is-- No homework and no exams, so yay.

All right.

Let's get started with cybersecurity fundamentals.

All right, we want to start with five security principles that you absolutely should do and one that you never should do.

So stay tuned to the end to find out what that one is.

The first one we're going to talk about is this notion of defense in depth.

Defense in depth is trying to create an obstacle course, a difficulty for the bad guy.

So if we take a look at an old security model, The castle.

Well, the castle was designed with thick tall walls to keep the good guys on the inside

and the bad guys on the outside.

And it worked pretty well until you realize the good guys sometimes needed to come out.

And therefore we needed to put a door on this thing.

Well, the door then became a vulnerability and so we would try to reinforce it and then maybe put a moat.

around the whole thing because that made it even harder.

And then the door with a drawbridge.

So now we've got a moat which is harder to cross.

We've got the thick tall walls.

And maybe we even added an angry dog here on this side.

Something to give a system of security mechanisms because defense in depth is all about not relying on any single security mechanism.

to keep the system safe.

Now let's move and transition into a modern security example.

Here we've got a user who is on a workstation, who's going to go across a network to get to a web server, which is going to hit an app server,

which is ultimately going to hit a database.

Now what would we do for defense in depth in this example?

Well, one thing I might do here is I might add multi -factor authentication.

That is a system where I make sure

that this user is who they are because I'm asking them for something they have, something they are, something they know, some combination of those kinds of things.

Now how about over here?

I might do, if it's a mobile device or an endpoint of some sort,

mobile device management, endpoint device management software, things like that.

We might also add something like an EDR, which is sort of a next generation antivirus,

an endpoint detection and response capability to make sure that this platform is secure.

Then from a network standpoint, well, I'm going to add in firewalls.

to keep the web server secure from the outside

and also allows only traffic that I choose to allow to get back to these more sensitive zones.

And then for the app server and the web server, I might do some testing,

some vulnerability testing on those so that I make sure that those systems are not vulnerable to attack.

And then ultimately, I'm going to take the data back here and I'm going to encrypt it.

lock it up, put access controls around it.

So you can see what I've done here is there's no single security mechanism that is protecting this thing.

If any one of these fails, the rest of the system still works.

And that's the idea that we're after here.

So if you think about it this way, we've got no single point of failure.

We're trying to avoid single points of failure.

And we want a system that ultimately, if it fails, it fails safe.

That's what we're trying to get and that's what the old model and the new model of securities were designed to do.

The second principle we're going to review is the principle of least privilege.

Principle of least privilege basically says I'm only going to give access rights to people that need that,

that are authorized and needed in order to do their job and can justify it, and for only as long as they need that access right.

For instance, in this example, I've got three users This guy is not really have a business need, so we don't give it to him.

The other guys get the access right.

They can prove their need.

And the other thing is, even for these guys, the clock is ticking.

I'm not going to give them this access right in perpetuity forever.

we're going to constantly be going back and making sure that they still need that capability.

If they don't, we're going to remove it from them as well.

Now another notion in the principle of least privilege is hardening a system.

Let's say we've got a web server like this.

And the web server out of the box, default configuration is that it runs HTTP of course because we need that in order to do web traffic.

But let's say it also turns on an FTP server.

and SSH service so that I can log in remotely.

Well, there's some things that I might look at and say, "Okay, do I really need this FTP server?

If it turns out I'm not going to use it, I should remove that service entirely.

In the SSH, if I'm not planning to use it, remove it entirely.

because every single one of these services is potentially expanding our attack surface and making us more vulnerable.

Another example of hardening is to remove all of the unnecessary IDs

that are on the system and change the names of the IDs that we do keep from their defaults.

So for instance, if the administrator ID on this system out of the box as it's configured is admin, Let's change that.

Let's make it something more specific.

and I'll name it after me or give it some other name, change all the default passwords.

We don't want this thing in just a vanilla configuration

because the bad guys will know what that is and they'll know how to break in.

Another example is this idea of privilege creep.

Let me illustrate that.

Let's say there's two people that work for the company and each one of these are access rights that they have.

So this guy is able to do these things, he can do the same things because they perform essentially the same role.

Now this guy gets a promotion and a new job and new responsibilities.

Well, he goes to the administrator and says, "Okay, now I'm doing my new job.

I need you to add to my capabilities." and these are the things I need.

The administrator gives him those and then also says, "You know what?

Just in case, I think you're going to probably need this, let me give you that as well.

That way you won't have to come back and ask again.

or "come back and bother me" is what he really means.

The problem with this is, just in case is just the opposite of principle of least privilege.

In fact, what we should be doing is running an annual recertification campaign. at least annual.

Some organizations do it more frequently than that.

And in research, I go back and look at all of my users

and all of their access rights and make sure they still have a justified need.

So this person still doing the same job, still needs all of that, great, they keep it.

This guy, though, no longer needs this capability because his new job doesn't require it, so we're taking it away.

100

And this thing that he got just in case, we're taking that away too.

101

So what we're trying to do with the principle of least

102

privilege is to give only the access rights you need for as long as you need them hardened systems, we're going to eliminate privilege creep,

103

and we're going to eliminate the just -in -case principle.

104

Our third principle to keep in mind with cybersecurity is this notion of separation of duties.

105

That is, we won't have any single point of control.

106

In fact, what we're trying to do is force collusion by two bad actors

107

or more than two bad actors in order to compromise the system.

108

But no single person can create the compromise.

109

So an example in the physical world would be

110

if I had two people here and I've got a door with two locks on it.

111

and this guy has a key to this lock, And this guy has a key to this lock.

112

and What it is is now if he uses his key to open the door, He still can't open the door.

113

He can't open the door alone.

114

But the two of them together cooperating can in fact open the door.

115

So there's no single point of control.

116

Therefore, we have a separation of duties.

117

Now, taking a look at another example here, let's say in an IT case, here's a requester and this user wants access to this database.

118

So he's going to ask for that.

119

He's going to send in his request, but then there's an approver who's going to have to take action on it and say yes or no, based upon whether we think they should have it or not.

120

Then if they get the approval, then they're given the action that they want.

121

You know, whatever it is, the funds transfer, the access to the database, the package delivered, whatever it happens to be.

122

But notice the point here.

123

This person, The requester is not the same as the approver.

124

they cannot be the same person because if it was, if I could request and approve my own request, then there is no separation of duties.

125

So again, what we're trying to do with this is create

126

a necessary case for collusion which is hard to do

127

because it's hard for lots of people to work together and keep a good secret.

128

And what we're trying to avoid is this single point of control.

129

The fourth security principle that we're going to talk about is secure by design.

130

In other words, it shouldn't be an afterthought that we put security in.

131

Think of it this way.

132

If you were designing a building in an earthquake zone, you want to make this building able to stand the pressure.

133

So, you don't go build the building and then after it's all done, go back and say, "Now let's make it earthquake proof." No,

134

you want to do that from start to finish all the way from design through completion.

135

So let's take a look at an IT example.

136

So when we have a project, you know, we will tend to start off with requirements stage.

137

We'll go then into design.

138

We'll code the thing, then we'll install whatever it is that we've written.

139

then we'll test it out and then we'll promote it to production.

140

And then in theory, we should feed that loop back and continue the continuous development process that way.

141

Well, what we don't want to do

142

is what too many people do in these cases and they wait until really about this phase to do security.

143

Once it's already out there, security can't just be a bolt on that you do at the end.

144

In fact, It needs to be something that we're doing throughout pervasively.

145

We look at the security aspects of the requirements, we build security into the design, We're thinking about secure coding principles all along the path.

146

When we install, we do it on a secure system.

147

We're testing and guarding that test data and then in production obviously we keep testing.

148

So security is something we do throughout But it doesn't begin here.

149

It begins in these phases.

150

That's what we're really looking for here.

151

Now if you think about another example, let's say Whose job is security?

152

Well, it's really everyone.

153

Here we have a designer, an administrator, and a user.

154

So really, all of them are responsible for security in one way or another.

155

But who does the job begin with?

156

Well, it begins with this guy right here.

157

We need to make sure that he is designing security in.

158

In other words, what we're trying to do is make security start to finish, And we want secure by design means it's secure out of the box.

159

That's the way we'd like it to be.

160

Now sometimes we're going to have to do some configuration changes to make it more secure, but This is the goal that we're trying to shoot for.

161

Secure by design, secure out of the box.

162

Our fifth security principle is the KISS principle.

163

It stands for Keep It Simple Stupid.

164

In other words, we don't want to make it harder than necessary

165

because that will make it easier for the bad guys and harder for the good guys.

166

To give you an example, we're trying to create some level of complexity so that it's not easy for the bad guy to get in.

167

But a lot of times the security department will create this complex maze of things

168

that the good guys essentially have to go through.

169

And what happens in that case is I start in here, okay, I log in, now I have to traverse and eventually I'm like,

170

"I'm at a dead end." Okay, maybe let's try this again.

171

You know what?

172

It's too much trouble to do what the security department has asked me to do.

173

I'm just going to subvert this and I'm going to end up doing it that way, which is of course not what we're after.

174

So the lesson here is if we make it harder to do the right thing than it is to do the

175

the wrong thing, People are going to do the wrong thing.

176

So we need to be able to make the system secure, but also as simple as possible.

177

So keep it simple stupid.

178

Here's an example of how we do this in security departments for real.

179

We'll come up with password rules.

180

So we'll say, "This is your password." and it equals this.

181

And it's this because we created a complex set of rules that say, you have to start with an upper case, then you follow with a lower case, then you need a special character,

182

then you need to throw in some numbers, and then you have to have some mixture of upper and lower case and special characters and all this kind of stuff, and it has to be really long.

183

And by the way, We need lots of these.

184

You're going to have a different one on every system and I'm going to make you change it on a frequent basis.

185

That's this.

186

That's what the user sees, is a complex maze.

187

And they're going to find a way to do this.

188

And what they're going to do is find one password

189

and write it down and set all their systems equal to the same thing, which is again, not what we were after.

190

So what we want to do is Understand complexity is the enemy of security.

191

So we want to make the system just complex enough to keep the bad guys out, but not so complex that it's hard for the good guys to do what they need to do.

192

For instance, you might have noticed, well, what about defense in depth, which I talked about up here?

193

There might be some conflict in that

194

because there we're trying to set a system of security mechanisms in place to put an obstacle course for the bad guy.

195

We want that obstacle course to be for the bad guy, not for the good guy.

196

All right, now we've gone over five security principles that you should always observe.

197

And now the big reveal the security principle you should never observe and that is security by obscurity.

198

that is relying on some sort of secret knowledge in order to make the system safe.

199

It turns out that secrecy and security are not the same thing.

200

In fact, what we want is a system that is open and observable

201

And this guy called Kirchhoff came up with what's now known as Kirchhoff's principle, which basically describes that.

202

He was specifically talking about a crypto system

203

and he said basically a crypto system should be secure if you know every single thing about it except for the key.

204

In other words, the key is the only secret in the whole system.

205

Now, why would this be an issue?

206

Well, it turns out a lot of people, and you should, whenever you hear this, you should run, not walk, but run away.

207

When you hear somebody say, I've invented a crypto system that's proprietary, and it will take your clear text, you feed it into my...

208

algorithm along with a key and then it will produce from clear text to ciphertext.

209

Okay, great.

210

The problem is this is a black box.

211

I can't see how it's working.

212

And if the individual says it's unbreakable, I've been hacking at it for weeks, months, years.

213

All that means is the inventor couldn't find a way to break it.

214

But that's not the same thing as the whole world given access would in fact break this.

215

And in fact, given time, they will, even if it is a black box.

216

History has shown that to be the case.

217

So what we want is not black box security, We want class box security.

218

So in this case, what we have is the clear text goes into a crypto algorithm which we understand.

219

It's been published.

220

In fact, if you look at the good crypto algorithms that we rely on today, it's things like AES, the Advanced Encryption Standard, and RSA.

221

These are algorithms that everyone that wants to know how they work can look it up and see.

222

And the secrecy, therefore the security, doesn't come from some secret knowledge of how this thing works.

223

It's able to produce ciphertext from cleartext without having to keep this part secret.

224

The only secret is the key and that's what we want.

225

We do the same kind of things when we talk about secure operating systems or secure applications or things like that,

226

as long as the security is based on secrecy, It's not really something that we can rely on.

227

Before you leave, don't forget to hit subscribe.

228

That way you won't miss the next installment of the Cybersecurity Architecture series.

📺 같은 채널

✨ 추천 영상

126 문장

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

Business EnglishUniversity StudentsWorking Adults

158 문장

OWASP Top 10 Explained

Business EnglishUniversity StudentsWorking Adults

180 문장

Armchair Architects: Resiliency in the Cloud – Core Patterns

Business EnglishUniversity StudentsWorking Adults

30 문장

The Art of War by Sun Tzu | Main Ideas

Business EnglishUniversity StudentsWorking Adults

8 문장

Every Cybersecurity Beginner Should Watch This First (Networking Fundamentals)

Business EnglishUniversity StudentsWorking Adults

30 문장

7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting

Business EnglishUniversity StudentsWorking Adults

162 문장

Crypto Agility Explained: Protect Data from Quantum Computing Threats

Business EnglishUniversity StudentsWorking Adults

60 문장

Course Preview | SC-100 | Microsoft Cybersecurity Architect

Cambridge Exam PrepBusiness EnglishUniversity Students

101 문장

BGP Overview

Business EnglishUniversity StudentsWorking Adults

173 문장

STOP Running Code On Your Computer

Business EnglishUniversity StudentsWorking Adults

110 문장

Architect Steven Harris’ 5 Non-Negotiables When Designing His Own Home (Design Masterclass)

Business EnglishUniversity StudentsWorking Adults

실생활 시나리오: 사이버보안 아키텍처 원칙 설명

이 비디오는 사이버공격 위협이 높아지는 현대 사회에서 기업 보안을 강화하기 위한 아키텍처 원칙을 설명하는 내용입니다. 강사가 대학 수업 내용을 바탕으로 "방어 심화"와 "최소 권한 원칙" 등을 구체적인 예시와 함께 설명하며, 전문 용어와 일상적인 설명이 혼합된 자연스러운 발화 패턴을 보여줍니다. 이는 기술 분야의 전문가가 일반인 또는 직원에게 개념을 전달할 때의 흔한 대화 방식을 반영하고 있습니다.

유용한 표현과 연어

defense in depth: "방어 심화"로 번역되며, 단일 보안 수단에 의존하지 않고 여러 계층의 방어 시스템을 구축하는 개념입니다. 예: "Defense in depth is all about not relying on any single security mechanism."
principle of least privilege: "최소 권한 원칙"으로, 업무에 필요한 최소한의 접근 권한만 부여하는 원칙입니다. 예: "Principle of least privilege basically says I'm only going to give access rights to people that need that."
multifactor authentication (MFA): "다중 인증"으로, 비밀번호 외에 지문, SMS 코드 등 추가 인증 수단을 사용하는 방식입니다. 예: "I might add multifactor authentication (MFA) to ensure the user is who they claim to be."
vulnerability testing: "취약점 테스트"로, 시스템의 보안 약점을 찾아내는 과정입니다. 예: "We might do some vulnerability testing on the app server."

당신의 쉐도잉 챌린지

유튜브 영어 공부에서 가장 효과적인 방법 중 하나는 쉐도잉입니다. 이 비디오의 0:30~1:30 구간을 선택해 다음 과정을 따라해 보세요. shadow speak 기술을 사용해 발화자의 음성, 억양, 속도를 정확히 모방하세요. 먼저 2~3번 반복해서 듣고, 그 다음 즉시 따라 말해보세요. 특히 "defense in depth"와 "principle of least privilege" 같은 전문 용어의 발음을 주의깊게 들으며, 문장의 흐름을 자연스럽게 따라가세요. 이 과정을 5분씩 하루에 2번 반복하면, 영어 듣기와 말하기 실력이 빠르게 향상될 것입니다. shadowspeaks 또는 shadow speech로 검색하면 더 많은 쉐도잉 팁을 찾을 수 있으니 참고하세요!

이 영상의 문법

화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.

문형	영상 속 표현
수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점	is protected · be applied · is based
현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때	I've done · we've written · has asked
관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보	moat which is · server, which is · EDR, which is

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

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

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

쉐도잉 연습: Cybersecurity Architecture: Five Principles to Follow (and One to Avoid) - 영상으로 영어 말하기 배우기

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

Cybersecurity Architecture: Data Security

The 7 Skills You Need to Build AI Agents

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

What are AI Agents?

Zero Trust Explained in 4 mins

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

OWASP Top 10 Explained

Armchair Architects: Resiliency in the Cloud – Core Patterns

The Art of War by Sun Tzu | Main Ideas

Every Cybersecurity Beginner Should Watch This First (Networking Fundamentals)

7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting

Crypto Agility Explained: Protect Data from Quantum Computing Threats

Course Preview | SC-100 | Microsoft Cybersecurity Architect

BGP Overview

STOP Running Code On Your Computer

Architect Steven Harris’ 5 Non-Negotiables When Designing His Own Home (Design Masterclass)

실생활 시나리오: 사이버보안 아키텍처 원칙 설명

유용한 표현과 연어

당신의 쉐도잉 챌린지

이 영상의 문법

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