WEBVTT

1
00:00:00.000 --> 00:00:02.480
<v Speaker 1>All right, listener name ready to dive into this whole

2
00:00:02.520 --> 00:00:05.919
<v Speaker 1>security transformation thing. Absolutely, you've been digging into all this

3
00:00:06.040 --> 00:00:11.000
<v Speaker 1>stuff about modern security practices Microsoft Solutions, getting ready for

4
00:00:11.039 --> 00:00:12.279
<v Speaker 1>that SC nine hundred exam.

5
00:00:12.359 --> 00:00:14.839
<v Speaker 2>Right, Yeah, looks like you've been spending some serious time

6
00:00:14.880 --> 00:00:19.120
<v Speaker 2>with that Microsoft Security Compliance and Identity Fundamentals Exam ref.

7
00:00:19.719 --> 00:00:20.920
<v Speaker 2>SC nine hundred book.

8
00:00:21.120 --> 00:00:24.039
<v Speaker 1>It's a gold mine, that's for sure. I mean, where

9
00:00:24.039 --> 00:00:25.760
<v Speaker 1>do you even start with something this big?

10
00:00:26.000 --> 00:00:27.719
<v Speaker 2>Well, what I found really interesting is how the book

11
00:00:27.800 --> 00:00:30.199
<v Speaker 2>kicks things off. It's like, remember back when we thought

12
00:00:30.239 --> 00:00:33.200
<v Speaker 2>we could just build a digital fortress around our computers

13
00:00:33.240 --> 00:00:35.920
<v Speaker 2>and data, like with a good firewall. We thought that

14
00:00:36.000 --> 00:00:37.079
<v Speaker 2>was enough, you know.

15
00:00:37.200 --> 00:00:39.920
<v Speaker 1>Oh, totally like those medieval castles with the moats and

16
00:00:39.960 --> 00:00:43.159
<v Speaker 1>the drawbridges. You're either in or you're out exactly.

17
00:00:43.840 --> 00:00:46.479
<v Speaker 2>But as the book makes clear, the way we work

18
00:00:46.560 --> 00:00:50.320
<v Speaker 2>now it's completely different. We're accessing sensitive information from everywhere.

19
00:00:50.439 --> 00:00:54.280
<v Speaker 1>Yeah, and from like every device imaginable, our phones, laptops,

20
00:00:54.479 --> 00:00:56.640
<v Speaker 1>even our smart watches. It's kind of crazy when you

21
00:00:56.679 --> 00:00:57.280
<v Speaker 1>think about.

22
00:00:57.079 --> 00:01:01.920
<v Speaker 2>It, right, So that old school fortress mentality, yeah, it

23
00:01:02.000 --> 00:01:05.000
<v Speaker 2>just doesn't cut it anymore. The book really drives that

24
00:01:05.040 --> 00:01:05.560
<v Speaker 2>point home.

25
00:01:05.760 --> 00:01:08.120
<v Speaker 1>Yeah, and it's not just theoretical either. You know, like

26
00:01:08.200 --> 00:01:10.760
<v Speaker 1>that story we saw about the rise and ransomware attacks,

27
00:01:10.760 --> 00:01:13.239
<v Speaker 1>it's happening everywhere now, even to smaller businesses.

28
00:01:13.519 --> 00:01:16.760
<v Speaker 2>Exactly. It's not just about protecting big corporate secrets anymore.

29
00:01:16.799 --> 00:01:20.359
<v Speaker 2>It's about safeguarding those everyday operations, the stuff that keeps

30
00:01:20.400 --> 00:01:21.239
<v Speaker 2>businesses running.

31
00:01:21.519 --> 00:01:24.840
<v Speaker 1>Makes you realize just how important this whole security transformation

32
00:01:24.959 --> 00:01:25.719
<v Speaker 1>thing really is.

33
00:01:25.959 --> 00:01:28.640
<v Speaker 2>It is, and that's really the core of what this

34
00:01:28.680 --> 00:01:31.920
<v Speaker 2>book is getting at. It's not about becoming a cybersecurity

35
00:01:31.959 --> 00:01:35.519
<v Speaker 2>expert overnight. It's more about equipping yourself with a new mindset,

36
00:01:35.920 --> 00:01:37.120
<v Speaker 2>a security.

37
00:01:36.640 --> 00:01:39.799
<v Speaker 1>Mindset, and that's something everyone needs, regardless of what you

38
00:01:39.840 --> 00:01:42.799
<v Speaker 1>do or where you work, right one hundred percent, So,

39
00:01:42.920 --> 00:01:46.519
<v Speaker 1>if we're ditching the whole fortress analogy, what's the new

40
00:01:46.560 --> 00:01:49.799
<v Speaker 1>way to think about security? There was this one phrase

41
00:01:49.840 --> 00:01:51.319
<v Speaker 1>in the book that really stuck with me.

42
00:01:51.560 --> 00:01:55.280
<v Speaker 2>Identity is the new perimeter. It's everywhere these days.

43
00:01:55.359 --> 00:01:57.480
<v Speaker 1>Yeah, that's the one. It's catchy and all, But what's

44
00:01:57.519 --> 00:01:59.840
<v Speaker 1>the practical side of it? How does that actually play out?

45
00:02:00.120 --> 00:02:03.040
<v Speaker 2>Think about it. Our online lives, everything from banking to

46
00:02:03.120 --> 00:02:06.519
<v Speaker 2>work stuff, even just scrolling through social media. It all

47
00:02:06.560 --> 00:02:09.840
<v Speaker 2>comes down to our logins, right, our identities.

48
00:02:10.039 --> 00:02:13.719
<v Speaker 1>Yeah, it's true. Our digital footprint is everywhere.

49
00:02:13.240 --> 00:02:16.080
<v Speaker 2>Exactly, So as we move more and more into this

50
00:02:16.159 --> 00:02:20.840
<v Speaker 2>cloud first world, that identity, it becomes the most important

51
00:02:20.840 --> 00:02:21.639
<v Speaker 2>thing to protect.

52
00:02:21.919 --> 00:02:24.520
<v Speaker 1>Okay, that makes sense. So it's like our digital fingerprint

53
00:02:24.639 --> 00:02:26.800
<v Speaker 1>is like the new key to the castle.

54
00:02:27.000 --> 00:02:30.080
<v Speaker 2>You're getting it. But here's where it gets even trickier.

55
00:02:30.719 --> 00:02:33.360
<v Speaker 2>Remember how you mentioned those stories about passwords getting hacked,

56
00:02:33.919 --> 00:02:35.520
<v Speaker 2>even those super complicated ones.

57
00:02:35.599 --> 00:02:38.080
<v Speaker 1>Yeah, it makes you feel like nothing is ever truly safe.

58
00:02:38.319 --> 00:02:42.039
<v Speaker 2>Right. Even a strong password isn't a guarantee anymore. Hackers

59
00:02:42.039 --> 00:02:44.879
<v Speaker 2>are getting too good. That's where IAM comes in, Identity

60
00:02:44.919 --> 00:02:45.879
<v Speaker 2>and Access Management.

61
00:02:46.080 --> 00:02:48.120
<v Speaker 1>IAM. Right, that was in the book. I have to

62
00:02:48.159 --> 00:02:50.360
<v Speaker 1>admit that one sounded a bit like a tech jumble

63
00:02:50.400 --> 00:02:51.039
<v Speaker 1>to me at first.

64
00:02:51.039 --> 00:02:53.280
<v Speaker 2>It's easy to get lost in the jargon, but the

65
00:02:53.319 --> 00:02:56.000
<v Speaker 2>idea itself is pretty straightforward. It all boils down to

66
00:02:56.520 --> 00:03:00.719
<v Speaker 2>least privilege. Least privilege, Okay, basically, you only give users

67
00:03:00.840 --> 00:03:04.560
<v Speaker 2>access to the specific data and systems they absolutely need

68
00:03:04.599 --> 00:03:08.120
<v Speaker 2>to do their jobs. Nothing more, nothing less, So no.

69
00:03:08.159 --> 00:03:10.599
<v Speaker 1>More giving everyone the master key to the castle.

70
00:03:10.840 --> 00:03:15.680
<v Speaker 2>Exactly. It's all about damage control by limiting access even

71
00:03:15.680 --> 00:03:18.919
<v Speaker 2>if someone does manage to slip through, you've minimized the

72
00:03:18.919 --> 00:03:19.840
<v Speaker 2>potential fallout.

73
00:03:20.000 --> 00:03:22.719
<v Speaker 1>That makes a lot of sense. So instead of blindly

74
00:03:22.759 --> 00:03:26.520
<v Speaker 1>trusting everyone inside the castle walls, we're being more strategic

75
00:03:26.520 --> 00:03:28.520
<v Speaker 1>about who gets in and what they can access.

76
00:03:28.639 --> 00:03:31.479
<v Speaker 2>Now you're getting it. And speaking of castle walls, remember

77
00:03:31.479 --> 00:03:34.400
<v Speaker 2>how the book talked about defense in depth. I thought

78
00:03:34.439 --> 00:03:35.719
<v Speaker 2>that was a really interesting concept.

79
00:03:35.800 --> 00:03:37.879
<v Speaker 1>Yeah, it sounds like it takes the castle analogy to

80
00:03:37.960 --> 00:03:38.800
<v Speaker 1>a whole new level.

81
00:03:38.919 --> 00:03:42.479
<v Speaker 2>It does. So imagine a real medieval castle, right, You

82
00:03:42.599 --> 00:03:44.840
<v Speaker 2>got your outer walls, yeah, but then you've got the moat,

83
00:03:44.960 --> 00:03:47.879
<v Speaker 2>the drawbridge, guard towers, maybe even a dungeon or two.

84
00:03:48.000 --> 00:03:51.199
<v Speaker 2>Sounds very elaborate, it was, And that's what defense and

85
00:03:51.240 --> 00:03:54.479
<v Speaker 2>depth is all about, creating multiple layers of security, each

86
00:03:54.520 --> 00:03:57.039
<v Speaker 2>one designed to protect against a different kind of threat.

87
00:03:57.319 --> 00:04:01.280
<v Speaker 1>Okay, so it's not about just one big, impenetrable wall,

88
00:04:01.479 --> 00:04:05.159
<v Speaker 1>but rather a series of smaller, more targeted defenses.

89
00:04:05.319 --> 00:04:07.560
<v Speaker 2>You got it. Think of it as a layered approach

90
00:04:07.639 --> 00:04:08.360
<v Speaker 2>to security.

91
00:04:08.520 --> 00:04:11.080
<v Speaker 1>So walk me through those layers a bit more. Where

92
00:04:11.120 --> 00:04:11.919
<v Speaker 1>do we even begin?

93
00:04:12.240 --> 00:04:14.080
<v Speaker 2>All right? Well, the first one is the most obvious

94
00:04:14.120 --> 00:04:17.600
<v Speaker 2>physical security, but in the cloud world, that's mainly the

95
00:04:17.639 --> 00:04:18.920
<v Speaker 2>provider's responsibility.

96
00:04:19.000 --> 00:04:21.120
<v Speaker 1>So we can take that one off the list pretty much.

97
00:04:21.480 --> 00:04:26.160
<v Speaker 2>Microsoft's got these massive data centers, top notch security. They've

98
00:04:26.199 --> 00:04:27.079
<v Speaker 2>got that part covered.

99
00:04:27.160 --> 00:04:28.399
<v Speaker 1>That's reassuring at least.

100
00:04:28.519 --> 00:04:31.240
<v Speaker 2>What's next, Well, we just talked about it. Identity and

101
00:04:31.279 --> 00:04:34.040
<v Speaker 2>access management, that's your new front line. Then you've got

102
00:04:34.079 --> 00:04:35.040
<v Speaker 2>perimeter security.

103
00:04:35.079 --> 00:04:38.439
<v Speaker 1>That sounds familiar. So we're talking firewalls here, yeah, but.

104
00:04:38.680 --> 00:04:42.360
<v Speaker 2>Not your grandpa's firewall. Yeah, these things are seriously sophisticated.

105
00:04:42.399 --> 00:04:45.839
<v Speaker 2>They're analyzing network traffic for anything suspicious.

106
00:04:45.319 --> 00:04:47.279
<v Speaker 1>So firewalls have gone high tech.

107
00:04:47.160 --> 00:04:51.639
<v Speaker 2>Big temp. Then moving inwards, you've got network security. It's

108
00:04:51.680 --> 00:04:53.600
<v Speaker 2>about segmenting your network, dividing it.

109
00:04:53.600 --> 00:04:56.120
<v Speaker 1>Up, Okay, like dividing the castle into separate.

110
00:04:55.759 --> 00:05:00.240
<v Speaker 2>Wings precisely that way, if one part gets compromised, the

111
00:05:00.279 --> 00:05:03.040
<v Speaker 2>intruder can't just waltz into every other area.

112
00:05:03.439 --> 00:05:07.879
<v Speaker 1>Containment is key smart strategy. So we've got the perimeter covered,

113
00:05:08.000 --> 00:05:11.560
<v Speaker 1>the network itself. But what about the actual data, the

114
00:05:11.639 --> 00:05:14.240
<v Speaker 1>servers where it all lives. How do we protect that?

115
00:05:14.560 --> 00:05:18.079
<v Speaker 2>Ah, excellent question. That's where compute security comes in. Making

116
00:05:18.079 --> 00:05:21.759
<v Speaker 2>sure the servers are locked down, tight configured, properly patched

117
00:05:21.839 --> 00:05:24.879
<v Speaker 2>up and the data itself is encrypted. Remember you asked

118
00:05:24.879 --> 00:05:26.600
<v Speaker 2>about encryption listener name right.

119
00:05:26.720 --> 00:05:30.680
<v Speaker 1>Encryption is like the ultimate shield for sensitive information, exactly

120
00:05:30.759 --> 00:05:31.279
<v Speaker 1>like having.

121
00:05:31.160 --> 00:05:33.560
<v Speaker 2>A digital vault. No one can crack love it.

122
00:05:34.000 --> 00:05:36.879
<v Speaker 1>Okay, so we've got all these layers in place. Everyone's

123
00:05:36.920 --> 00:05:40.600
<v Speaker 1>doing their part, but who ultimately calls the shots. Who's

124
00:05:40.639 --> 00:05:44.680
<v Speaker 1>responsible for making sure this whole intricate security setup actually works?

125
00:05:44.800 --> 00:05:47.199
<v Speaker 2>Ah? Now this is where it gets really interesting. The

126
00:05:47.199 --> 00:05:50.600
<v Speaker 2>book dives into this whole concept of shared responsibility in

127
00:05:50.639 --> 00:05:51.000
<v Speaker 2>the cloud.

128
00:05:51.160 --> 00:05:53.079
<v Speaker 1>Shared responsibility huh yep.

129
00:05:53.399 --> 00:05:56.920
<v Speaker 2>So Microsoft as the cloud provider, they take care of

130
00:05:56.959 --> 00:06:00.000
<v Speaker 2>their end of the bargain, think physical security, the infrastructures,

131
00:06:00.759 --> 00:06:04.079
<v Speaker 2>but when it comes to managing your data, controlling user access,

132
00:06:04.600 --> 00:06:06.480
<v Speaker 2>that responsibility still falls on you.

133
00:06:06.920 --> 00:06:08.720
<v Speaker 1>So it's more of a partnership than anything.

134
00:06:08.920 --> 00:06:11.480
<v Speaker 2>You got it. It's a joint effort and the level

135
00:06:11.480 --> 00:06:14.920
<v Speaker 2>of responsibility it actually changes depending on what kind of

136
00:06:14.920 --> 00:06:17.319
<v Speaker 2>cloud service you're using. And remember how the book talked

137
00:06:17.319 --> 00:06:19.839
<v Speaker 2>about iis pious.

138
00:06:19.839 --> 00:06:24.120
<v Speaker 1>And sauce vaguely acronyms aren't exactly my forte, no worries, it's.

139
00:06:24.000 --> 00:06:26.399
<v Speaker 2>A lot to keep straight. Think of it like this,

140
00:06:26.519 --> 00:06:30.360
<v Speaker 2>ias infrastructure as a service it's like building your own house.

141
00:06:30.399 --> 00:06:33.240
<v Speaker 2>You've got all the control, but you're also responsible for everything.

142
00:06:33.360 --> 00:06:33.839
<v Speaker 1>Makes sense.

143
00:06:34.240 --> 00:06:37.000
<v Speaker 2>Then there's pious platform as a service that's more like

144
00:06:37.000 --> 00:06:40.480
<v Speaker 2>rending a furnished department, and sauce software as a service

145
00:06:40.560 --> 00:06:42.879
<v Speaker 2>that's like checking into a hotel. They handle most of

146
00:06:42.879 --> 00:06:43.920
<v Speaker 2>the stuff, you just show up.

147
00:06:44.160 --> 00:06:47.319
<v Speaker 1>Okay, that analogy actually makes it much clearer. Different levels

148
00:06:47.360 --> 00:06:50.319
<v Speaker 1>of control, different levels of responsibility exactly.

149
00:06:51.040 --> 00:06:54.439
<v Speaker 2>But even with the best defenses, a solid understanding of

150
00:06:54.639 --> 00:06:57.600
<v Speaker 2>who's doing what, there's always a chance something could slip through.

151
00:06:57.920 --> 00:06:59.240
<v Speaker 1>Yeah, that's a bit unsettling.

152
00:06:59.319 --> 00:07:02.759
<v Speaker 2>It's the nature beast. Unfortunately. That's why this next principle

153
00:07:02.800 --> 00:07:05.519
<v Speaker 2>the book talks about is so important. Zero trust.

154
00:07:06.160 --> 00:07:08.879
<v Speaker 1>Zero trust. Huh, that sounds pretty intense.

155
00:07:09.040 --> 00:07:10.800
<v Speaker 2>It is a big change from how we used to

156
00:07:10.800 --> 00:07:14.600
<v Speaker 2>think about security. Instead of assuming trust within your network,

157
00:07:15.000 --> 00:07:19.839
<v Speaker 2>zero trust is all about verifying everything and everyone all

158
00:07:19.879 --> 00:07:21.600
<v Speaker 2>the time, no exceptions.

159
00:07:21.639 --> 00:07:23.800
<v Speaker 1>Wait, so you're saying I shouldn't even trust my own devices.

160
00:07:23.839 --> 00:07:26.000
<v Speaker 1>That seems a bit extreme, doesn't it. I mean it

161
00:07:26.040 --> 00:07:28.040
<v Speaker 1>sounds a little like we're assuming everyone is out to

162
00:07:28.079 --> 00:07:28.519
<v Speaker 1>get us.

163
00:07:28.759 --> 00:07:31.600
<v Speaker 2>Well, think of it less about suspicion and more about

164
00:07:31.639 --> 00:07:32.279
<v Speaker 2>being prepared.

165
00:07:32.439 --> 00:07:32.680
<v Speaker 1>Yeah.

166
00:07:32.720 --> 00:07:34.560
<v Speaker 2>Remember that news story you shared, the one about that

167
00:07:34.600 --> 00:07:36.519
<v Speaker 2>really convincing fishing scam.

168
00:07:36.600 --> 00:07:38.800
<v Speaker 1>Oh yeah, that was a tricky.

169
00:07:38.480 --> 00:07:41.920
<v Speaker 2>One, right, Things aren't always what they seem. Zero trust

170
00:07:42.199 --> 00:07:45.920
<v Speaker 2>just acknowledges that trust can be broken. It's about adopting

171
00:07:45.920 --> 00:07:49.399
<v Speaker 2>this mindset of never trust, always verify.

172
00:07:50.160 --> 00:07:52.319
<v Speaker 1>Okay, that makes sense. So how does this zero trust

173
00:07:52.399 --> 00:07:54.839
<v Speaker 1>thing actually work? How do you even put that into practice?

174
00:07:54.920 --> 00:07:57.399
<v Speaker 2>So the book breaks it down into three parts. First,

175
00:07:57.480 --> 00:08:00.680
<v Speaker 2>there's the signal. It's basically an indication that something might

176
00:08:00.720 --> 00:08:03.240
<v Speaker 2>be a little off. Think of it like those motion

177
00:08:03.319 --> 00:08:06.560
<v Speaker 2>detectors you have for your home security system listener name.

178
00:08:06.519 --> 00:08:09.519
<v Speaker 1>Right, Like an alert that something's not quite right exactly.

179
00:08:09.560 --> 00:08:12.199
<v Speaker 2>So, for example, maybe there's an unexpected log in attempt

180
00:08:12.240 --> 00:08:15.399
<v Speaker 2>from a new device, or someone's trying to access files

181
00:08:15.439 --> 00:08:18.600
<v Speaker 2>they shouldn't have permission for those, red flag exactly. So

182
00:08:18.639 --> 00:08:21.720
<v Speaker 2>that's the signal. Then you've got the decision phase. Okay,

183
00:08:21.800 --> 00:08:23.839
<v Speaker 2>based on that signal, what are we going to do

184
00:08:23.920 --> 00:08:28.720
<v Speaker 2>about it? Block the access attempt altogether, require some extra verification,

185
00:08:29.399 --> 00:08:31.720
<v Speaker 2>like using multi factor authentication.

186
00:08:31.680 --> 00:08:34.000
<v Speaker 1>Which, let me tell you, as someone who forgets their

187
00:08:34.000 --> 00:08:37.879
<v Speaker 1>passwords constantly, I'm a big fan of MFA. It's a

188
00:08:37.879 --> 00:08:39.039
<v Speaker 1>life saver, it really is.

189
00:08:39.440 --> 00:08:42.159
<v Speaker 2>And finally you've got the enforcement piece, which is basically

190
00:08:42.200 --> 00:08:45.519
<v Speaker 2>putting that decision into action, the actual security measure that

191
00:08:45.559 --> 00:08:46.240
<v Speaker 2>gets triggered.

192
00:08:46.360 --> 00:08:48.039
<v Speaker 1>Okay, so it's a whole process, kind of like a

193
00:08:48.080 --> 00:08:49.840
<v Speaker 1>digital security checkpoint exactly.

194
00:08:50.240 --> 00:08:54.120
<v Speaker 2>Zero trust isn't just about being skeptical. It's about having

195
00:08:54.120 --> 00:08:57.399
<v Speaker 2>a system in place to analyze and respond to those

196
00:08:57.440 --> 00:08:58.360
<v Speaker 2>potential threats.

197
00:08:58.559 --> 00:09:01.919
<v Speaker 1>So we're not just relying on blind trust anymore. We've

198
00:09:01.919 --> 00:09:04.320
<v Speaker 1>got these systems in place to back us up.

199
00:09:04.519 --> 00:09:07.840
<v Speaker 2>Precisely, speaking of systems, remember how the book got into

200
00:09:07.840 --> 00:09:11.240
<v Speaker 2>all those Microsoft security tools. I have to say, they've

201
00:09:11.279 --> 00:09:12.639
<v Speaker 2>really got you covered on that front.

202
00:09:12.799 --> 00:09:15.320
<v Speaker 1>Yeah. I was blown away by that. It wasn't just theory.

203
00:09:15.399 --> 00:09:17.799
<v Speaker 1>It was like, here's what you can actually use to

204
00:09:17.840 --> 00:09:20.919
<v Speaker 1>put these principles into practice. Were there any tools that

205
00:09:20.960 --> 00:09:21.600
<v Speaker 1>stood out to you?

206
00:09:21.919 --> 00:09:25.240
<v Speaker 2>Oh? Definitely. Azure Active Directory or Azure AD as it's

207
00:09:25.279 --> 00:09:26.679
<v Speaker 2>usually called, is a big.

208
00:09:26.480 --> 00:09:29.559
<v Speaker 1>One, right, And you know, I love a good acronym.

209
00:09:29.600 --> 00:09:30.559
<v Speaker 1>But what is it? Exactly?

210
00:09:30.679 --> 00:09:33.600
<v Speaker 2>Etically, it's your command center for managing all those digital

211
00:09:33.639 --> 00:09:35.240
<v Speaker 2>identities and access permissions.

212
00:09:35.440 --> 00:09:38.519
<v Speaker 1>Ah So, going back to that idea of identity is

213
00:09:38.559 --> 00:09:41.519
<v Speaker 1>the new perimeter. This is how we manage it all exactly.

214
00:09:41.559 --> 00:09:43.840
<v Speaker 2>Think of it as the nervous system of your whole

215
00:09:43.879 --> 00:09:47.240
<v Speaker 2>security setup. And to make it even stronger, there's Azure

216
00:09:47.279 --> 00:09:51.519
<v Speaker 2>AD Multi Factor Authentication MFA. You already mentioned you're a fan.

217
00:09:51.559 --> 00:09:52.679
<v Speaker 1>Can't live without it.

218
00:09:52.679 --> 00:09:57.279
<v Speaker 2>It's essential that extra layer of security beyond just the password,

219
00:09:57.399 --> 00:09:59.080
<v Speaker 2>you know, like needing that code from your phone or

220
00:09:59.120 --> 00:09:59.879
<v Speaker 2>email apps.

221
00:10:00.519 --> 00:10:03.799
<v Speaker 1>Okay, so that helps with those more direct threats. But

222
00:10:03.919 --> 00:10:07.039
<v Speaker 1>what about those sneakier attacks, the ones that are harder

223
00:10:07.080 --> 00:10:07.639
<v Speaker 1>to detect.

224
00:10:07.720 --> 00:10:12.639
<v Speaker 2>Well, Microsoft's got something for that too, Azure AD Identity Protection. Okay,

225
00:10:12.759 --> 00:10:16.799
<v Speaker 2>and this does it's constantly analyzing user behavior, looking for

226
00:10:16.960 --> 00:10:19.879
<v Speaker 2>anything out of the ordinary, like if someone starts acting

227
00:10:19.919 --> 00:10:23.519
<v Speaker 2>suspiciously accessing things they don't normally access. Is like having

228
00:10:23.559 --> 00:10:26.679
<v Speaker 2>a security guard who's always watching even when you don't

229
00:10:26.720 --> 00:10:27.240
<v Speaker 2>realize it.

230
00:10:27.440 --> 00:10:31.039
<v Speaker 1>That's pretty impressive. So we're talking next level security here exactly.

231
00:10:31.279 --> 00:10:34.159
<v Speaker 2>And to protect all those Azure resources you're using, there

232
00:10:34.240 --> 00:10:37.600
<v Speaker 2>is Microsoft Defender for Cloud. It's designed specifically for the

233
00:10:37.639 --> 00:10:41.600
<v Speaker 2>Azure environment, so it's constantly scanning for vulnerabilities, making sure

234
00:10:41.639 --> 00:10:42.919
<v Speaker 2>everything's locked down tight.

235
00:10:43.000 --> 00:10:45.720
<v Speaker 1>Okay, so that's Azure covered. But what about all the

236
00:10:45.759 --> 00:10:48.399
<v Speaker 1>other cloud apps we're all using these days, you know,

237
00:10:48.480 --> 00:10:50.279
<v Speaker 1>the ones that aren't directly tied to Azure.

238
00:10:50.639 --> 00:10:53.840
<v Speaker 2>You're right, those are easy overlook. But thankfully Microsoft has

239
00:10:53.840 --> 00:10:57.159
<v Speaker 2>a solution for that too, Microsoft Defender for Cloud Apps.

240
00:10:57.360 --> 00:11:00.600
<v Speaker 1>Ah, so nothing slips through the cracks exactly.

241
00:11:00.679 --> 00:11:02.960
<v Speaker 2>It's like having a watchful eye on all your cloud apps,

242
00:11:03.120 --> 00:11:04.919
<v Speaker 2>even those ones that might have knuck in through the

243
00:11:04.960 --> 00:11:05.399
<v Speaker 2>back door.

244
00:11:05.559 --> 00:11:08.480
<v Speaker 1>No more shadow it, then love it. Yeah, and I

245
00:11:08.519 --> 00:11:11.440
<v Speaker 1>know the book also mentioned Microsoft three sixty five Defender.

246
00:11:11.519 --> 00:11:12.440
<v Speaker 1>What's that all about?

247
00:11:12.799 --> 00:11:15.399
<v Speaker 2>That one's your go to for all things Microsoft three

248
00:11:15.480 --> 00:11:20.480
<v Speaker 2>sixty five. It's like a security blanket specifically for your email, documents,

249
00:11:20.919 --> 00:11:23.320
<v Speaker 2>collaboration tools, the whole shebang.

250
00:11:23.360 --> 00:11:27.039
<v Speaker 1>Okay, so we've got security covered from all angles. But

251
00:11:27.360 --> 00:11:29.440
<v Speaker 1>there was another big theme in the book that really

252
00:11:29.639 --> 00:11:33.360
<v Speaker 1>resonated with me. Compliance. It feels like a whole other

253
00:11:33.480 --> 00:11:35.960
<v Speaker 1>beast to tackle, especially for someone like me who's still

254
00:11:36.000 --> 00:11:38.240
<v Speaker 1>getting up to speed on all things cybersecurity.

255
00:11:38.360 --> 00:11:42.480
<v Speaker 2>It's definitely important. Yeah, it can feel overwhelming, but here's

256
00:11:42.480 --> 00:11:45.639
<v Speaker 2>the good news. Microsoft offers tools to help you navigate

257
00:11:45.679 --> 00:11:48.399
<v Speaker 2>that maze. Have you heard of Compliance Manager?

258
00:11:48.720 --> 00:11:50.799
<v Speaker 1>It rings a bell, but refresh my memory.

259
00:11:50.559 --> 00:11:53.120
<v Speaker 2>It's basically your compliance sidekick. It helps you keep track

260
00:11:53.159 --> 00:11:56.320
<v Speaker 2>of all those industry standards regulations, making sure you're ticking

261
00:11:56.320 --> 00:11:57.200
<v Speaker 2>all the right boxes.

262
00:11:57.320 --> 00:11:59.440
<v Speaker 1>Ah. So it takes some of the guesswork out of compliance.

263
00:11:59.480 --> 00:12:00.919
<v Speaker 1>That's reasty sure exactly.

264
00:12:00.960 --> 00:12:02.679
<v Speaker 2>Compliance doesn't have to be a headache.

265
00:12:02.799 --> 00:12:06.120
<v Speaker 1>This has been an amazing deep dive. It's clear why

266
00:12:06.159 --> 00:12:09.000
<v Speaker 1>this book is so helpful for anyone tackling that SC

267
00:12:09.080 --> 00:12:11.519
<v Speaker 1>nine hundred exam, or even if they just want to

268
00:12:11.600 --> 00:12:13.159
<v Speaker 1>level up their cybersecurity know.

269
00:12:13.120 --> 00:12:16.600
<v Speaker 2>How agreed, it's really practical, but it also brings up

270
00:12:16.639 --> 00:12:18.840
<v Speaker 2>some really important questions, like the one the book leaves

271
00:12:18.879 --> 00:12:21.519
<v Speaker 2>us with, how do we balance all these robust security

272
00:12:21.559 --> 00:12:24.679
<v Speaker 2>measures with the need to respect user privacy.

273
00:12:24.919 --> 00:12:27.200
<v Speaker 1>It's a fine line, for sure, and such a relevant

274
00:12:27.240 --> 00:12:29.799
<v Speaker 1>topic these days. I mean, it's clear security is not

275
00:12:29.840 --> 00:12:34.000
<v Speaker 1>a one time thing, it's an ongoing journey. Well, on

276
00:12:34.039 --> 00:12:36.039
<v Speaker 1>that note, thanks for joining me on this deep dive.

277
00:12:36.159 --> 00:12:37.799
<v Speaker 1>Listener name until next time.