WEBVTT

1
00:00:00.000 --> 00:00:03.279
<v Speaker 1>All right, strap in everyone, let's take a deep dive

2
00:00:03.520 --> 00:00:11.640
<v Speaker 1>into this open Source Security Testing Methodology Manual THEMM. Yeah, STMM,

3
00:00:11.679 --> 00:00:14.000
<v Speaker 1>that's a mouthful. It is kind of like a security

4
00:00:14.039 --> 00:00:16.879
<v Speaker 1>decoder ring, right, I mean, the thing is dense. Yeah,

5
00:00:16.879 --> 00:00:18.879
<v Speaker 1>but don't worry. We're going to break it down. Make

6
00:00:18.920 --> 00:00:22.600
<v Speaker 1>it makes sense. You shared some concerns about I think

7
00:00:22.640 --> 00:00:26.120
<v Speaker 1>it was mentioned a specific detail from listener source material

8
00:00:26.280 --> 00:00:31.359
<v Speaker 1>related to security, right, and the OSSTMM. It can actually

9
00:00:31.679 --> 00:00:33.679
<v Speaker 1>help you understand that stuff a little better.

10
00:00:33.840 --> 00:00:37.520
<v Speaker 2>Absolutely. It's put together by security testers for security testers,

11
00:00:37.560 --> 00:00:39.000
<v Speaker 2>real world stuff, real world.

12
00:00:38.880 --> 00:00:42.719
<v Speaker 1>Stuff, so less theory, more like in the trenches kind

13
00:00:42.719 --> 00:00:43.119
<v Speaker 1>of stuff.

14
00:00:43.200 --> 00:00:45.000
<v Speaker 2>Yeah, that's how security works in the real world.

15
00:00:45.079 --> 00:00:47.159
<v Speaker 1>That's good. That's good. So one of the first things

16
00:00:47.200 --> 00:00:49.359
<v Speaker 1>that kind of jumps out at you, you know, going

17
00:00:49.399 --> 00:00:55.719
<v Speaker 1>through the OSSTMM, is this focus on operational security op sec. Yeah,

18
00:00:56.039 --> 00:00:57.799
<v Speaker 1>what exactly does that mean? I mean, is an all

19
00:00:57.840 --> 00:00:59.600
<v Speaker 1>security operational? In some way?

20
00:01:00.119 --> 00:01:02.399
<v Speaker 2>I think the OSSTM and really draws a line.

21
00:01:02.479 --> 00:01:02.840
<v Speaker 1>Okay.

22
00:01:03.159 --> 00:01:05.200
<v Speaker 2>You know a lot of times security is presented like

23
00:01:05.239 --> 00:01:09.959
<v Speaker 2>this wall, solid wall between your assets, your data and

24
00:01:10.000 --> 00:01:14.719
<v Speaker 2>the bad guys. Okay, but in reality that wall is

25
00:01:14.719 --> 00:01:18.439
<v Speaker 2>full of holes. Ah, okay, and the OSS TMN calls

26
00:01:18.480 --> 00:01:22.959
<v Speaker 2>those holes trusts, trust and optic. It's all about, you know,

27
00:01:23.040 --> 00:01:25.959
<v Speaker 2>looking at those trusts, figuring out how strong they are,

28
00:01:26.000 --> 00:01:27.640
<v Speaker 2>figuring out if they're actually holding up.

29
00:01:27.840 --> 00:01:30.680
<v Speaker 1>So instead of just assuming things are secure, you've got

30
00:01:30.719 --> 00:01:33.519
<v Speaker 1>to really look closer at those trusts exactly and see

31
00:01:33.519 --> 00:01:34.879
<v Speaker 1>if they're actually doing their job.

32
00:01:35.159 --> 00:01:37.519
<v Speaker 2>Yeah, you're trusting something to do what it says it's

33
00:01:37.560 --> 00:01:37.959
<v Speaker 2>going to do.

34
00:01:38.120 --> 00:01:40.680
<v Speaker 1>Okay, Okay, can you give me like a real world example,

35
00:01:40.760 --> 00:01:43.519
<v Speaker 1>like what would a trust look like in the real world?

36
00:01:43.959 --> 00:01:46.879
<v Speaker 2>I mean, even something you mentioned in your notes, like

37
00:01:47.079 --> 00:01:51.120
<v Speaker 2>relying on a specific piece of software for your business. Yeah,

38
00:01:51.200 --> 00:01:54.640
<v Speaker 2>you know, that's a trust. You're trusting that software to

39
00:01:54.799 --> 00:01:57.359
<v Speaker 2>do what it's supposed to do and to do it securely.

40
00:01:57.959 --> 00:02:01.480
<v Speaker 2>But what if that software has vulnerabilities? Oh what if

41
00:02:01.480 --> 00:02:03.920
<v Speaker 2>the company behind that software has you know, kind of

42
00:02:03.959 --> 00:02:07.920
<v Speaker 2>shady security practices, that trust becomes a weak point.

43
00:02:08.120 --> 00:02:11.280
<v Speaker 1>Okay, Yeah, that makes sense. So opsec is really pushing

44
00:02:11.319 --> 00:02:15.280
<v Speaker 1>you to look beyond the surface question those assumptions.

45
00:02:15.479 --> 00:02:16.080
<v Speaker 2>Absolutely.

46
00:02:16.159 --> 00:02:20.120
<v Speaker 1>So how does the OSTMM actually help you do that? Like,

47
00:02:20.199 --> 00:02:23.159
<v Speaker 1>how do you assess these trusts and figure out where

48
00:02:23.199 --> 00:02:24.039
<v Speaker 1>you're vulnerable?

49
00:02:24.199 --> 00:02:27.800
<v Speaker 2>That's where this idea of the four point process comes in. Okay,

50
00:02:27.800 --> 00:02:29.759
<v Speaker 2>because a lot of security assessments are kind of like

51
00:02:30.120 --> 00:02:33.080
<v Speaker 2>yelling into a cave and waiting for the echo. You're

52
00:02:33.080 --> 00:02:36.639
<v Speaker 2>only getting this very limited perspective, right, and the OSSTMM

53
00:02:36.680 --> 00:02:38.599
<v Speaker 2>says that's not good enough. You've got to get up

54
00:02:38.599 --> 00:02:40.319
<v Speaker 2>close and personal with your security.

55
00:02:40.400 --> 00:02:43.159
<v Speaker 1>Okay, So less like superficial checks, more like a deep

56
00:02:43.199 --> 00:02:45.280
<v Speaker 1>dive into how things are working.

57
00:02:45.400 --> 00:02:46.960
<v Speaker 2>Yeah, how are things actually functioning?

58
00:02:47.400 --> 00:02:49.800
<v Speaker 1>Okay? I like that, I like that, But how does

59
00:02:49.840 --> 00:02:51.960
<v Speaker 1>this four point process actually work?

60
00:02:52.560 --> 00:02:56.599
<v Speaker 2>It breaks it down into these four stages. Okay, in quest, intervention, induction,

61
00:02:56.960 --> 00:02:57.560
<v Speaker 2>and interaction.

62
00:02:57.759 --> 00:02:59.759
<v Speaker 1>Wow, okay, break those down for me.

63
00:03:00.240 --> 00:03:03.680
<v Speaker 2>So inquest is all about gathering information you really want

64
00:03:03.680 --> 00:03:06.680
<v Speaker 2>to understand the system you're trying to secure. Intervention is

65
00:03:06.719 --> 00:03:09.000
<v Speaker 2>where you actually simulate real world attacks.

66
00:03:09.319 --> 00:03:11.479
<v Speaker 1>Oh so you're actually like trying to break things.

67
00:03:11.599 --> 00:03:13.919
<v Speaker 2>You're trying to see how your security holds up under pressure.

68
00:03:14.039 --> 00:03:15.280
<v Speaker 1>Okay, now it's getting real.

69
00:03:16.280 --> 00:03:19.879
<v Speaker 2>Then you have induction, where you're analyzing all the data

70
00:03:19.879 --> 00:03:22.560
<v Speaker 2>that you've gathered, figuring out what it means. And then

71
00:03:22.599 --> 00:03:26.599
<v Speaker 2>finally there's interaction, which is really understanding how people and

72
00:03:27.280 --> 00:03:32.919
<v Speaker 2>processes impact security. Like you mentioned reference a security related

73
00:03:33.039 --> 00:03:36.800
<v Speaker 2>human element detail from the listener's source material. Right, that

74
00:03:36.919 --> 00:03:38.639
<v Speaker 2>fits right into this interaction piece.

75
00:03:39.039 --> 00:03:41.479
<v Speaker 1>Okay, So this four point process is giving you this

76
00:03:41.680 --> 00:03:44.879
<v Speaker 1>much more in depth view of your security. It's not

77
00:03:45.039 --> 00:03:48.159
<v Speaker 1>just about finding the holes. It's about understanding.

78
00:03:47.639 --> 00:03:51.520
<v Speaker 3>The whole systems, understanding every dingy inside and out exactly.

79
00:03:51.639 --> 00:03:55.960
<v Speaker 2>Yeah. And out of that process comes something called the RAF.

80
00:03:55.319 --> 00:03:58.159
<v Speaker 2>The RAF it's like your security scorecard.

81
00:03:58.199 --> 00:04:00.520
<v Speaker 1>Okay, hold on, we can't just breeze pass the RAV.

82
00:04:00.919 --> 00:04:03.479
<v Speaker 1>You compared it to a credit score for security.

83
00:04:03.560 --> 00:04:06.840
<v Speaker 2>Yeah, it's a way to measure how exposed are you,

84
00:04:07.639 --> 00:04:09.319
<v Speaker 2>how good is your security posture?

85
00:04:09.400 --> 00:04:12.639
<v Speaker 1>All right, but how is it actually calculated? And what

86
00:04:12.879 --> 00:04:14.560
<v Speaker 1>does that number actually tell you?

87
00:04:14.960 --> 00:04:18.199
<v Speaker 2>So think of it like this. A RAVE of one

88
00:04:18.279 --> 00:04:23.279
<v Speaker 2>hundred is perfect balance, everything is working perfectly. Oh, your controls,

89
00:04:24.040 --> 00:04:26.879
<v Speaker 2>you know, they're aligned with your operations. Anything less than

90
00:04:26.920 --> 00:04:30.319
<v Speaker 2>one hundred, that means you've got gaps, gaps, there are

91
00:04:30.360 --> 00:04:31.879
<v Speaker 2>areas where you're more vulnerable.

92
00:04:31.959 --> 00:04:34.040
<v Speaker 1>So the lower the RAVE, the more work I need

93
00:04:34.079 --> 00:04:34.279
<v Speaker 1>to do.

94
00:04:34.480 --> 00:04:36.680
<v Speaker 2>Yeah, basically I'm getting the picture.

95
00:04:36.920 --> 00:04:39.199
<v Speaker 1>What I find interesting is that you said this can

96
00:04:39.240 --> 00:04:42.160
<v Speaker 1>be applied to anything, right, You know, a massive data center,

97
00:04:42.399 --> 00:04:45.720
<v Speaker 1>a small business, even your own home. Exactly how is

98
00:04:45.759 --> 00:04:48.959
<v Speaker 1>that possible? How can one score apply to all these

99
00:04:49.000 --> 00:04:50.120
<v Speaker 1>different situations?

100
00:04:50.480 --> 00:04:54.879
<v Speaker 2>Because the RAV isn't tied to specific technology or specific systems,

101
00:04:55.279 --> 00:04:58.240
<v Speaker 2>it's really a framework for understanding how well your security

102
00:04:58.319 --> 00:05:00.199
<v Speaker 2>is working compared to what you need.

103
00:05:00.399 --> 00:05:01.720
<v Speaker 1>Okay, relative to your needs.

104
00:05:01.800 --> 00:05:03.879
<v Speaker 2>Yeah, so you could look at the RAV of your

105
00:05:03.879 --> 00:05:07.360
<v Speaker 2>home network, you know, and think about how strong are

106
00:05:07.399 --> 00:05:10.600
<v Speaker 2>your passwords? Is your Wi Fi secure? Do you leave

107
00:05:10.639 --> 00:05:11.639
<v Speaker 2>your front door unlocked?

108
00:05:11.839 --> 00:05:14.199
<v Speaker 1>Okay, So it's not just about the tech, it's about

109
00:05:14.199 --> 00:05:15.519
<v Speaker 1>the whole picture.

110
00:05:15.839 --> 00:05:18.600
<v Speaker 2>Yeah, every habits and all that, it all plays a part.

111
00:05:18.720 --> 00:05:21.879
<v Speaker 1>Okay, this is really making me rethink my own security habits,

112
00:05:21.879 --> 00:05:25.360
<v Speaker 1>I'll be honest. Now, another big concept in the OSSTMM

113
00:05:25.439 --> 00:05:28.519
<v Speaker 1>is trust. Right, but it's not the kind of like

114
00:05:29.120 --> 00:05:31.399
<v Speaker 1>touchy feely trust we usually talk about.

115
00:05:31.480 --> 00:05:34.199
<v Speaker 2>Right, We're not talking about feelings here, Okay. This is

116
00:05:34.240 --> 00:05:40.199
<v Speaker 2>about the OSSTMN breaks down trust into ten quantifiable properties.

117
00:05:40.240 --> 00:05:40.920
<v Speaker 1>Ten properties.

118
00:05:41.000 --> 00:05:44.600
<v Speaker 2>Yeah. It's taking something fuzzy, something subjective, ye, and turning

119
00:05:44.639 --> 00:05:47.279
<v Speaker 2>it into something you can actually measure and analyze.

120
00:05:47.639 --> 00:05:50.560
<v Speaker 1>Okay, Okay, so we're taking these vague ideas and making

121
00:05:50.600 --> 00:05:54.560
<v Speaker 1>them concrete exactly. But ten properties. That sounds a little overwhelming.

122
00:05:54.639 --> 00:05:55.519
<v Speaker 2>It's a lot to take in.

123
00:05:55.600 --> 00:05:57.160
<v Speaker 1>Can you give me an example, like, how do these

124
00:05:57.199 --> 00:05:59.160
<v Speaker 1>properties play out in the real world.

125
00:05:59.279 --> 00:06:01.879
<v Speaker 2>So let's go back to that software company. Okay, you're

126
00:06:01.879 --> 00:06:05.600
<v Speaker 2>trusting them with your data, maybe even your business operations,

127
00:06:06.160 --> 00:06:08.480
<v Speaker 2>but how do you know if that trust is well placed?

128
00:06:08.800 --> 00:06:08.959
<v Speaker 4>Right?

129
00:06:09.040 --> 00:06:09.480
<v Speaker 1>Good point.

130
00:06:09.639 --> 00:06:12.360
<v Speaker 2>So one of the trust properties is transparency.

131
00:06:12.439 --> 00:06:13.920
<v Speaker 1>Transparency, Okay, is.

132
00:06:13.879 --> 00:06:17.680
<v Speaker 2>The company open about their security practices? Do they have

133
00:06:17.720 --> 00:06:22.439
<v Speaker 2>a privacy policy that you can actually understand? Another property

134
00:06:22.600 --> 00:06:26.240
<v Speaker 2>is competence. Competence, have they actually built secure software in

135
00:06:26.279 --> 00:06:28.800
<v Speaker 2>the past, you know, do they have a track record

136
00:06:28.800 --> 00:06:32.160
<v Speaker 2>of not getting breached? All of these things play into

137
00:06:32.240 --> 00:06:33.879
<v Speaker 2>whether or not a company is trustworthy.

138
00:06:33.959 --> 00:06:36.120
<v Speaker 1>So you're looking at these properties, you're building a more

139
00:06:36.120 --> 00:06:38.879
<v Speaker 1>informed picture of whether this company is actually worthy of

140
00:06:38.920 --> 00:06:39.560
<v Speaker 1>your trust.

141
00:06:39.720 --> 00:06:41.600
<v Speaker 2>Absolutely, this is wow.

142
00:06:41.639 --> 00:06:45.040
<v Speaker 1>This is really making me rethink how I approach trust

143
00:06:45.560 --> 00:06:47.000
<v Speaker 1>in all areas of my life.

144
00:06:46.920 --> 00:06:48.120
<v Speaker 2>A different way of thinking about it.

145
00:06:48.279 --> 00:06:52.319
<v Speaker 1>Yeah. Yeah, And we haven't even touched on the ostmm's

146
00:06:52.560 --> 00:06:56.639
<v Speaker 1>deep dive into the five security channels five five we

147
00:06:56.720 --> 00:07:00.439
<v Speaker 1>got human security, physical security, wireless.

148
00:07:00.000 --> 00:07:03.800
<v Speaker 4>Security, telecommunications again in a network security YEP, that's all five.

149
00:07:03.959 --> 00:07:06.079
<v Speaker 1>Okay, So we got op SEC, we got this four

150
00:07:06.120 --> 00:07:10.240
<v Speaker 1>point process, we got RAVS. Now you're telling me there's

151
00:07:10.399 --> 00:07:12.439
<v Speaker 1>five security channels to consider.

152
00:07:12.879 --> 00:07:15.199
<v Speaker 4>It's a lot, but it's all connected. We got to

153
00:07:15.240 --> 00:07:17.959
<v Speaker 4>unpack those absolutely. Where do we even start, Well, let's

154
00:07:17.959 --> 00:07:20.959
<v Speaker 4>start with human security h U M SEC, DOM SCC

155
00:07:21.160 --> 00:07:23.639
<v Speaker 4>Yeah okay, since we were just talking about the human element.

156
00:07:23.399 --> 00:07:25.680
<v Speaker 1>Okay, Yeah, this is where it gets really interesting. Goes

157
00:07:25.720 --> 00:07:27.160
<v Speaker 1>beyond just the technical stuff.

158
00:07:27.199 --> 00:07:29.639
<v Speaker 2>It's not just about bits and bytes right right, It's

159
00:07:29.680 --> 00:07:32.959
<v Speaker 2>about psychology, social factors.

160
00:07:33.439 --> 00:07:37.240
<v Speaker 1>So it's understanding how people actually behave yeah, how they

161
00:07:37.319 --> 00:07:41.000
<v Speaker 1>make decisions, and how those decisions can actually like impact

162
00:07:41.040 --> 00:07:42.800
<v Speaker 1>security exactly. Okay.

163
00:07:42.879 --> 00:07:46.800
<v Speaker 2>Remember that software company we were talking about. Yeah, HTMSEC

164
00:07:47.480 --> 00:07:51.800
<v Speaker 2>would consider things like what's their internal security culture? Like, oh, okay,

165
00:07:52.360 --> 00:07:55.160
<v Speaker 2>do the employees actually understand security? Right?

166
00:07:55.279 --> 00:07:55.519
<v Speaker 1>Right?

167
00:07:55.600 --> 00:07:57.319
<v Speaker 2>You know, do they follow the best practices?

168
00:07:57.399 --> 00:07:57.800
<v Speaker 1>They care?

169
00:07:58.120 --> 00:07:59.319
<v Speaker 2>Do they care? Exactly?

170
00:07:59.399 --> 00:07:59.600
<v Speaker 1>Yeah?

171
00:08:00.040 --> 00:08:03.360
<v Speaker 2>Also looks at social engineering, okay, you know, are they

172
00:08:03.480 --> 00:08:07.480
<v Speaker 2>vulnerable to phishing scams or other things that try to

173
00:08:07.519 --> 00:08:08.519
<v Speaker 2>manipulate people?

174
00:08:09.240 --> 00:08:12.759
<v Speaker 1>You know, I mentioned in my notes that I was

175
00:08:12.759 --> 00:08:16.639
<v Speaker 1>a little worried about mention a specific detail from listeners

176
00:08:16.680 --> 00:08:21.680
<v Speaker 1>source material related to human element of security, right.

177
00:08:21.560 --> 00:08:25.279
<v Speaker 2>And the OSS TMM gives you a framework to think

178
00:08:25.319 --> 00:08:29.959
<v Speaker 2>about those very concerns and actually figure out some strategies

179
00:08:29.959 --> 00:08:30.600
<v Speaker 2>to address them.

180
00:08:30.600 --> 00:08:32.000
<v Speaker 1>Okay, that's reassuring.

181
00:08:32.120 --> 00:08:33.600
<v Speaker 2>All right, let's shift gears a little bit.

182
00:08:33.639 --> 00:08:37.480
<v Speaker 1>Okay, let's talk about physical security fiochy s se al.

183
00:08:37.559 --> 00:08:39.960
<v Speaker 2>Right. This is all about those you know, tangible.

184
00:08:39.480 --> 00:08:41.600
<v Speaker 1>Barriers, the stuff you can actually touch.

185
00:08:41.720 --> 00:08:44.840
<v Speaker 2>Yeah, the locks, the fences, the cameras, yeah, the guards,

186
00:08:44.879 --> 00:08:45.159
<v Speaker 2>all of that.

187
00:08:45.240 --> 00:08:48.759
<v Speaker 1>Okay, So, like the classic security measures, how does the

188
00:08:48.799 --> 00:08:51.039
<v Speaker 1>OSTMM approach this differently?

189
00:08:51.240 --> 00:08:53.919
<v Speaker 2>Well, it really makes you think like an attacker, Okay,

190
00:08:54.039 --> 00:08:57.440
<v Speaker 2>you know, forces you to consider all the weaknesses in

191
00:08:57.480 --> 00:08:58.600
<v Speaker 2>your physical defenses.

192
00:08:58.720 --> 00:09:01.879
<v Speaker 1>It's the stuff you might overloko if you're not thinking carefully.

193
00:09:02.120 --> 00:09:04.480
<v Speaker 2>Yeah, Because it's not just about having a lock on

194
00:09:04.519 --> 00:09:07.600
<v Speaker 2>the door. It's about how easy would it be for

195
00:09:07.639 --> 00:09:08.159
<v Speaker 2>someone to.

196
00:09:08.120 --> 00:09:10.840
<v Speaker 1>Pick that lock right, or just break the door down.

197
00:09:10.720 --> 00:09:13.240
<v Speaker 2>Exactly or find another way in. Yeah, you mentioned in

198
00:09:13.240 --> 00:09:16.200
<v Speaker 2>your notes that you mentioned a specific detail from Listener's

199
00:09:16.240 --> 00:09:20.240
<v Speaker 2>source material related to physical security. Yeah, so the Oasis

200
00:09:20.320 --> 00:09:23.039
<v Speaker 2>TMM would say, Okay, how easy would it be for

201
00:09:23.120 --> 00:09:27.240
<v Speaker 2>someone to like tailgate you tailgate right? Or are there

202
00:09:27.279 --> 00:09:30.320
<v Speaker 2>any blind spots in your security camera coverage.

203
00:09:30.360 --> 00:09:32.679
<v Speaker 1>Okay, yeah, this is kind of making me nervous now

204
00:09:32.759 --> 00:09:35.799
<v Speaker 1>a little bit, right, but better to know now than later, right, Oh? Absolutely,

205
00:09:36.000 --> 00:09:39.279
<v Speaker 1>all right, So let's talk about wireless security spec SIIC

206
00:09:39.840 --> 00:09:43.080
<v Speaker 1>spec SEC. Okay, this one seems super relevant these days.

207
00:09:43.120 --> 00:09:45.600
<v Speaker 1>Oh yeah, everyone's on Wi Fi, right, my dog's on

208
00:09:45.639 --> 00:09:45.960
<v Speaker 1>Wi Fi.

209
00:09:46.120 --> 00:09:49.279
<v Speaker 2>But spec SC isn't just about your home WiFi. Okay,

210
00:09:49.399 --> 00:09:54.159
<v Speaker 2>we're talking about Bluetooth RFID tags, even things like microwave ovens.

211
00:09:54.840 --> 00:09:57.240
<v Speaker 1>Hold on microwave oven.

212
00:09:57.080 --> 00:09:58.200
<v Speaker 2>They EMIT signals.

213
00:09:58.320 --> 00:10:01.000
<v Speaker 1>So my kitchen appliances are a security risks, maybe at

214
00:10:01.000 --> 00:10:04.840
<v Speaker 1>your microwave specifically, But the point is SPETS recognizes that

215
00:10:05.320 --> 00:10:08.559
<v Speaker 1>wireless signals are everywhere they are, yeah.

216
00:10:08.200 --> 00:10:10.519
<v Speaker 2>And those signals can be vulnerable. Oh you know, someone

217
00:10:10.519 --> 00:10:12.879
<v Speaker 2>could be eavesdropping. There could be interference.

218
00:10:12.960 --> 00:10:15.600
<v Speaker 1>So it's not just about having a strong Wi Fi password.

219
00:10:15.720 --> 00:10:19.200
<v Speaker 2>It's about the bigger picture. Okay, yeah, have broader risks

220
00:10:19.240 --> 00:10:20.600
<v Speaker 2>of wireless technology.

221
00:10:20.720 --> 00:10:23.360
<v Speaker 1>I see a pattern here. The os STMM is all

222
00:10:23.399 --> 00:10:28.879
<v Speaker 1>about thinking holistically absolutely. Okay, what about telecommunications security?

223
00:10:29.279 --> 00:10:32.039
<v Speaker 3>Come s e come se Okay, this one might seem

224
00:10:32.080 --> 00:10:34.519
<v Speaker 3>a little outdated, right, yeah, but it's all about those

225
00:10:34.559 --> 00:10:38.639
<v Speaker 3>systems we sometimes forget about, okay, phone lines, voicemail, even

226
00:10:38.679 --> 00:10:39.399
<v Speaker 3>fax machines.

227
00:10:39.559 --> 00:10:41.879
<v Speaker 2>Oh right, they can still be vulnerable.

228
00:10:41.960 --> 00:10:45.080
<v Speaker 1>Fax machines. I totally forgot about those. We're so focused

229
00:10:45.080 --> 00:10:49.320
<v Speaker 1>on our computers and our networks. But these other communication channels, yeah,

230
00:10:49.320 --> 00:10:51.519
<v Speaker 1>they could be weak points too, Exactly.

231
00:10:51.799 --> 00:10:53.639
<v Speaker 2>You got to think about all of it, okay. And

232
00:10:53.679 --> 00:10:57.440
<v Speaker 2>then finally there's data network security. Okay, this is probably

233
00:10:57.440 --> 00:11:00.440
<v Speaker 2>what most people think of when they hear cybersecurity. Yeah,

234
00:11:00.480 --> 00:11:04.120
<v Speaker 2>the main event, right, all about securing the networks, the servers, the.

235
00:11:04.120 --> 00:11:09.600
<v Speaker 1>Data, So firewalls, intrusion detection, encryption, all that stuff.

236
00:11:09.679 --> 00:11:09.960
<v Speaker 2>All that.

237
00:11:10.080 --> 00:11:15.120
<v Speaker 1>Yeah, okay, but what makes the ostmm's approach to this different.

238
00:11:15.159 --> 00:11:17.440
<v Speaker 1>I mean, it seems like everyone's got a cybersecurity solution

239
00:11:17.480 --> 00:11:18.000
<v Speaker 1>these days.

240
00:11:18.559 --> 00:11:21.879
<v Speaker 2>The OSSTMM doesn't just tell you what to do. It

241
00:11:21.919 --> 00:11:23.840
<v Speaker 2>teaches you how to think about security.

242
00:11:24.000 --> 00:11:24.279
<v Speaker 1>Okay.

243
00:11:24.879 --> 00:11:29.440
<v Speaker 2>It's a methodology, a framework for actually assessing your network,

244
00:11:29.600 --> 00:11:32.679
<v Speaker 2>got it, understanding the risks, and then figuring out what

245
00:11:32.759 --> 00:11:33.600
<v Speaker 2>controls you need.

246
00:11:33.720 --> 00:11:35.919
<v Speaker 1>So it's like giving you the knowledge to be your

247
00:11:35.960 --> 00:11:37.519
<v Speaker 1>own security expert.

248
00:11:37.639 --> 00:11:40.879
<v Speaker 2>Exactly. You take control, okay, instead of just blindly following

249
00:11:40.919 --> 00:11:41.919
<v Speaker 2>someone else's checklist.

250
00:11:42.000 --> 00:11:46.039
<v Speaker 1>I like that taking control. That's good. This has been Wow,

251
00:11:46.120 --> 00:11:47.200
<v Speaker 1>this has been an eye opener.

252
00:11:47.240 --> 00:11:48.279
<v Speaker 2>There's a lot to take in.

253
00:11:48.559 --> 00:11:51.360
<v Speaker 1>Yeah. I thought I was pretty good with security, you know,

254
00:11:51.559 --> 00:11:54.759
<v Speaker 1>strong passwords, anti virus. I thought I was all set right,

255
00:11:55.039 --> 00:11:57.279
<v Speaker 1>But there's so much more to consider.

256
00:11:57.480 --> 00:11:58.679
<v Speaker 2>It's a whole world out there.

257
00:11:58.759 --> 00:12:01.679
<v Speaker 1>Yeah. Yeah, it is, and we've only scratched the surface,

258
00:12:02.039 --> 00:12:04.480
<v Speaker 1>just the beginning. So there are seventeen modules in the

259
00:12:04.480 --> 00:12:07.120
<v Speaker 1>OSSTMS seventeen Yeah, okay, So that's where the rubber meets

260
00:12:07.159 --> 00:12:07.440
<v Speaker 1>the road.

261
00:12:07.559 --> 00:12:08.679
<v Speaker 2>That's where it gets practical.

262
00:12:08.840 --> 00:12:11.559
<v Speaker 1>Okay. So you take all this information and then you

263
00:12:11.600 --> 00:12:12.840
<v Speaker 1>actually turn it into action.

264
00:12:13.120 --> 00:12:16.200
<v Speaker 2>Yeah. The modules are like your toolbox Okay, for actually

265
00:12:16.279 --> 00:12:17.639
<v Speaker 2>implementing these principles.

266
00:12:17.679 --> 00:12:18.919
<v Speaker 1>Gotcha. So like a mix a match.

267
00:12:19.000 --> 00:12:21.480
<v Speaker 2>Yeah, you can choose which modules make sense for your situation.

268
00:12:21.919 --> 00:12:25.639
<v Speaker 1>Customized security checkout exactly. Okay, I like that. I like that. So,

269
00:12:25.799 --> 00:12:30.000
<v Speaker 1>for example, you mentioned the compliance verification module that helps

270
00:12:30.039 --> 00:12:33.440
<v Speaker 1>you make sure you're meeting all the legal and industry

271
00:12:33.480 --> 00:12:36.000
<v Speaker 1>standards and knowing the rules right right, which is a

272
00:12:36.039 --> 00:12:36.639
<v Speaker 1>big one for me.

273
00:12:36.919 --> 00:12:40.080
<v Speaker 2>Yeah, you mentioned that you were concerned about reference a

274
00:12:40.159 --> 00:12:43.519
<v Speaker 2>compliance related detail from the listener's source material.

275
00:12:43.279 --> 00:12:45.039
<v Speaker 1>Exactly, got to make sure I'm taking all the.

276
00:12:45.000 --> 00:12:49.919
<v Speaker 2>Right boxes, right. But the OSSTMM goes beyond just ticking boxes.

277
00:12:50.039 --> 00:12:50.360
<v Speaker 1>Okay.

278
00:12:50.399 --> 00:12:55.279
<v Speaker 2>Good. It's about understanding why those regulations exist and then

279
00:12:55.320 --> 00:12:59.320
<v Speaker 2>achieving real security, not just compliance for compliance's.

280
00:12:58.679 --> 00:13:00.399
<v Speaker 1>Sake, right, because at the end of the day, it's

281
00:13:00.399 --> 00:13:02.080
<v Speaker 1>about actually being secure.

282
00:13:02.480 --> 00:13:03.080
<v Speaker 2>Absolutely.

283
00:13:03.120 --> 00:13:06.440
<v Speaker 1>Okay. So another example, Let's say I'm worried about the

284
00:13:06.440 --> 00:13:09.759
<v Speaker 1>physical security of my home office, which i am. Yeah,

285
00:13:09.840 --> 00:13:11.120
<v Speaker 1>you mentioned that in my notes I did.

286
00:13:11.200 --> 00:13:15.279
<v Speaker 2>Yeah. So the OSSTMM has this module called Physical Security

287
00:13:15.360 --> 00:13:19.360
<v Speaker 2>Verification okay, and it walks you through this process of

288
00:13:19.440 --> 00:13:23.840
<v Speaker 2>assessing your vulnerabilities.

289
00:13:23.039 --> 00:13:25.480
<v Speaker 1>Like are there any easy access points?

290
00:13:25.720 --> 00:13:26.120
<v Speaker 2>Exact?

291
00:13:26.200 --> 00:13:29.879
<v Speaker 1>Could someone tamper with my equipment? Or my cameras actually

292
00:13:29.960 --> 00:13:31.080
<v Speaker 1>pointed in the right direction?

293
00:13:31.279 --> 00:13:32.240
<v Speaker 2>All good questions.

294
00:13:32.320 --> 00:13:35.000
<v Speaker 1>Okay. So it's like having a security expert looking over

295
00:13:35.039 --> 00:13:35.879
<v Speaker 1>your shoulder.

296
00:13:35.559 --> 00:13:37.200
<v Speaker 2>Yeah, pointing out the things you might miss.

297
00:13:37.399 --> 00:13:40.639
<v Speaker 1>Yeah. Yeah. But it's not just about finding the problems,

298
00:13:40.639 --> 00:13:41.919
<v Speaker 1>it's about fixing them too.

299
00:13:42.360 --> 00:13:47.679
<v Speaker 2>Absolutely. Each module gives you recommendations best practices okay, and

300
00:13:47.720 --> 00:13:50.120
<v Speaker 2>then it takes it even a step further with this

301
00:13:50.120 --> 00:13:51.919
<v Speaker 2>thing called characterizing results.

302
00:13:52.120 --> 00:13:53.960
<v Speaker 1>Characterizing results, what's that?

303
00:13:54.320 --> 00:13:56.960
<v Speaker 2>So you've done your security test. You found some issues,

304
00:13:57.399 --> 00:13:59.120
<v Speaker 2>but now you've got to figure out what did those

305
00:13:59.159 --> 00:14:03.399
<v Speaker 2>results actually mean. It's not just oh we found a vulnerability,

306
00:14:03.519 --> 00:14:07.960
<v Speaker 2>it's how serious is this vulnerability? How likely is it

307
00:14:08.000 --> 00:14:10.720
<v Speaker 2>that someone's going to try to exploit it? Right?

308
00:14:10.919 --> 00:14:13.519
<v Speaker 1>And if they do exploit it, what's the impact going

309
00:14:13.559 --> 00:14:13.759
<v Speaker 1>to be?

310
00:14:13.960 --> 00:14:17.519
<v Speaker 2>So you're putting the findings into context exactly, prioritizing the risks,

311
00:14:17.679 --> 00:14:20.679
<v Speaker 2>got it? Not just finding every little problem but figuring

312
00:14:20.679 --> 00:14:22.240
<v Speaker 2>out which problems are the biggest.

313
00:14:22.480 --> 00:14:24.080
<v Speaker 1>You got to focus on the big ones first.

314
00:14:24.279 --> 00:14:26.559
<v Speaker 2>Yeah, that makes sense. Yeah, this is one of the

315
00:14:26.559 --> 00:14:29.519
<v Speaker 2>things that makes the OSSTMM so powerful.

316
00:14:29.720 --> 00:14:30.080
<v Speaker 3>Yeah.

317
00:14:30.159 --> 00:14:34.919
<v Speaker 2>It helps you make informed decisions about security based on evidence,

318
00:14:35.480 --> 00:14:36.200
<v Speaker 2>not just fear.

319
00:14:36.320 --> 00:14:37.200
<v Speaker 1>You're not just guessing.

320
00:14:37.360 --> 00:14:40.279
<v Speaker 2>Okay, but let's be real, a lot of this sounds

321
00:14:40.279 --> 00:14:41.080
<v Speaker 2>pretty technical.

322
00:14:41.200 --> 00:14:41.960
<v Speaker 1>It is. Yeah.

323
00:14:42.159 --> 00:14:46.320
<v Speaker 2>Is the OSSTMM really something that the average person can

324
00:14:46.480 --> 00:14:49.799
<v Speaker 2>use or is this just for you know, the security pros.

325
00:14:49.919 --> 00:14:51.519
<v Speaker 1>That's one of the great things about it.

326
00:14:51.559 --> 00:14:51.759
<v Speaker 2>Okay.

327
00:14:51.759 --> 00:14:54.799
<v Speaker 1>It's designed to be accessible, Okay, no matter what your

328
00:14:54.799 --> 00:14:56.039
<v Speaker 1>technical skill level is.

329
00:14:56.200 --> 00:14:56.519
<v Speaker 2>Okay.

330
00:14:56.639 --> 00:15:00.600
<v Speaker 1>It uses clear language, real world examples to explain these

331
00:15:00.639 --> 00:15:01.960
<v Speaker 1>complicated concepts.

332
00:15:02.360 --> 00:15:04.639
<v Speaker 2>So even if I'm not a security expert. I can

333
00:15:04.720 --> 00:15:08.559
<v Speaker 2>still use this to improve my security absolutely. Okay. That's

334
00:15:08.600 --> 00:15:10.799
<v Speaker 2>good to hear. And in fact, one of the core

335
00:15:10.879 --> 00:15:15.080
<v Speaker 2>principles of the OSSTMM is that security should be a

336
00:15:15.159 --> 00:15:18.480
<v Speaker 2>collaborative effort. Okay, it's not just about one person.

337
00:15:18.279 --> 00:15:20.240
<v Speaker 1>Or one team, right, We're all in this together.

338
00:15:20.320 --> 00:15:23.159
<v Speaker 2>Everyone needs to work together, okay, to make things more

339
00:15:23.200 --> 00:15:24.159
<v Speaker 2>secure for everyone.

340
00:15:24.240 --> 00:15:28.159
<v Speaker 1>That's reassuring, right, Yeah. Yeah, I gotta admit I'm still

341
00:15:28.159 --> 00:15:29.559
<v Speaker 1>a little intimidated by all this.

342
00:15:30.320 --> 00:15:30.840
<v Speaker 2>I get it.

343
00:15:30.840 --> 00:15:32.000
<v Speaker 1>It's a lot to take it.

344
00:15:32.080 --> 00:15:34.679
<v Speaker 2>Yeah, it's a dense document. Yeah, there's a lot to.

345
00:15:34.679 --> 00:15:37.240
<v Speaker 1>Learn, but I don't need to master every detail.

346
00:15:37.639 --> 00:15:40.919
<v Speaker 2>You don't have to know everything, Okay, even just understanding

347
00:15:40.919 --> 00:15:44.759
<v Speaker 2>the basic principles and applying a few the key concepts

348
00:15:45.039 --> 00:15:46.279
<v Speaker 2>that can make a huge difference.

349
00:15:46.399 --> 00:15:49.080
<v Speaker 1>Okay, that's good to hear. Right, Yeah, yeah, but let's

350
00:15:49.120 --> 00:15:53.799
<v Speaker 1>not sugarcoat it, Okay. Implementing the OSSTMM. It takes work.

351
00:15:54.120 --> 00:15:54.440
<v Speaker 2>It does.

352
00:15:54.519 --> 00:15:56.720
<v Speaker 1>Yeah, it's not just reading the manual and calling it

353
00:15:56.759 --> 00:16:00.000
<v Speaker 1>a day. It's not magic, no, No, it takes effort,

354
00:16:00.039 --> 00:16:01.279
<v Speaker 1>it takes commitment.

355
00:16:01.000 --> 00:16:03.879
<v Speaker 2>It takes a willingness to actually change how you think

356
00:16:03.919 --> 00:16:08.720
<v Speaker 2>about security. But the rewards are worth it. The OSSTMM

357
00:16:08.799 --> 00:16:12.679
<v Speaker 2>can help you build a more secure organization, protect your

358
00:16:12.840 --> 00:16:16.440
<v Speaker 2>valuable assets, and it can even give you a competitive edge.

359
00:16:16.559 --> 00:16:18.960
<v Speaker 1>Okay, all right, I'm sold. I'm ready to dive in

360
00:16:19.200 --> 00:16:21.159
<v Speaker 1>good But where do I even begin?

361
00:16:21.639 --> 00:16:24.919
<v Speaker 2>Well, the OSSTMM has this thing called a posture review.

362
00:16:25.360 --> 00:16:27.720
<v Speaker 2>It's the first step, and that's where you gather all

363
00:16:27.720 --> 00:16:31.600
<v Speaker 2>the information about your organization. What are your assets, what's

364
00:16:31.639 --> 00:16:32.960
<v Speaker 2>your security environment like?

365
00:16:33.039 --> 00:16:36.080
<v Speaker 1>So you're taking stock of the current situation exactly.

366
00:16:36.080 --> 00:16:38.639
<v Speaker 2>You got to know where you're starting from before you

367
00:16:38.639 --> 00:16:39.720
<v Speaker 2>can figure out where you're going.

368
00:16:39.799 --> 00:16:43.799
<v Speaker 1>Okay, I get that. What happens after the posture review?

369
00:16:43.879 --> 00:16:46.039
<v Speaker 1>When does the actual testing start.

370
00:16:46.360 --> 00:16:48.159
<v Speaker 2>That's where the logistics phase comes in.

371
00:16:48.279 --> 00:16:49.440
<v Speaker 1>Logistics, Okay, this.

372
00:16:49.360 --> 00:16:53.000
<v Speaker 2>Is where you plan and prepare for the assessment. You're

373
00:16:53.039 --> 00:16:57.000
<v Speaker 2>defining the scope, You're picking the target systems and networks.

374
00:16:57.399 --> 00:16:59.240
<v Speaker 2>You're choosing your tools and techniques.

375
00:16:59.320 --> 00:17:01.480
<v Speaker 1>So it's like creating a battle plan exactly.

376
00:17:01.639 --> 00:17:04.599
<v Speaker 2>Okay, you've got to have a plan. Good logistics are

377
00:17:04.680 --> 00:17:07.680
<v Speaker 2>key to making sure the assessment is done thoroughly and efficiently.

378
00:17:07.880 --> 00:17:11.440
<v Speaker 1>Makes sense. Okay, So we've got the posture review, We've

379
00:17:11.440 --> 00:17:15.680
<v Speaker 1>got the logistics phase, right, what's next? In the OSSTMM

380
00:17:15.759 --> 00:17:16.759
<v Speaker 1>methodology flow.

381
00:17:17.200 --> 00:17:19.839
<v Speaker 2>Next comes the active detection verification phase.

382
00:17:19.960 --> 00:17:21.640
<v Speaker 1>Okay, active detection.

383
00:17:21.519 --> 00:17:24.799
<v Speaker 2>This is where you're actually testing your security. You know,

384
00:17:24.880 --> 00:17:27.640
<v Speaker 2>how good are you're monitoring and detecting capabilities?

385
00:17:27.720 --> 00:17:29.599
<v Speaker 1>So are my alarms actually working?

386
00:17:29.799 --> 00:17:32.480
<v Speaker 2>Yeah? And are you actually paying attention to those alarms? Right?

387
00:17:32.599 --> 00:17:32.839
<v Speaker 1>Right?

388
00:17:32.920 --> 00:17:37.200
<v Speaker 2>This involved things like testing your intrusion detection systems okay,

389
00:17:37.400 --> 00:17:41.079
<v Speaker 2>looking at your security logs, seeing if you're analyzing them properly,

390
00:17:41.799 --> 00:17:45.039
<v Speaker 2>even simulating incidents to see how quickly you can respond.

391
00:17:45.240 --> 00:17:48.119
<v Speaker 1>So it's about being proactive at testing things before an

392
00:17:48.119 --> 00:17:51.440
<v Speaker 1>actual attack happens exactly. Okay, that makes sense. But what

393
00:17:51.519 --> 00:17:55.240
<v Speaker 1>if we discover during this phase that our detection capabilities

394
00:17:55.400 --> 00:17:57.519
<v Speaker 1>they're just not up to snuff. What happens?

395
00:17:57.599 --> 00:18:01.079
<v Speaker 2>Then that's where the OSSTMMS recommendations come in.

396
00:18:01.160 --> 00:18:01.559
<v Speaker 1>Okay.

397
00:18:01.680 --> 00:18:05.240
<v Speaker 2>It gives you guidance on how to actually improve your security.

398
00:18:04.519 --> 00:18:05.440
<v Speaker 1>Based on the findings.

399
00:18:05.480 --> 00:18:06.839
<v Speaker 2>Yeah, based on what you've learned.

400
00:18:07.039 --> 00:18:07.279
<v Speaker 1>Okay.

401
00:18:07.400 --> 00:18:11.880
<v Speaker 2>It might involve upgrading your security tools okay, refining your processes,

402
00:18:12.519 --> 00:18:14.440
<v Speaker 2>maybe providing more training for your team.

403
00:18:14.599 --> 00:18:17.279
<v Speaker 1>So the OSSTMM doesn't just point out.

404
00:18:17.440 --> 00:18:19.160
<v Speaker 2>Problems, it helps you find solutions.

405
00:18:19.319 --> 00:18:21.599
<v Speaker 1>Okay, I like that it's a practical guide, not just

406
00:18:21.640 --> 00:18:26.079
<v Speaker 1>theoretical exactly. Okay, so we've got active detection verification. What's

407
00:18:26.119 --> 00:18:28.440
<v Speaker 1>the next step in this methodology flow.

408
00:18:28.640 --> 00:18:31.680
<v Speaker 2>That's where we get into channel and vector verification.

409
00:18:32.000 --> 00:18:32.960
<v Speaker 1>Channel invector.

410
00:18:33.759 --> 00:18:35.960
<v Speaker 2>Remember we talked about those security channels earlier.

411
00:18:36.119 --> 00:18:39.440
<v Speaker 1>Yeah, yeah, human security, physical security, all that exactly. Those

412
00:18:39.440 --> 00:18:39.920
<v Speaker 1>were eye.

413
00:18:39.799 --> 00:18:43.559
<v Speaker 2>Opening, they were, right. Yeah. So in this phase, you're

414
00:18:43.599 --> 00:18:47.920
<v Speaker 2>assessing the controls for each relevant channel and vector.

415
00:18:48.000 --> 00:18:50.480
<v Speaker 1>So you're making sure that you've got the right security

416
00:18:50.480 --> 00:18:53.519
<v Speaker 1>measures for all the different ways that your assets could

417
00:18:53.559 --> 00:18:54.079
<v Speaker 1>be attacked.

418
00:18:54.160 --> 00:18:57.759
<v Speaker 2>You got it. It's a comprehensive security checkup, okay, making

419
00:18:57.799 --> 00:19:00.440
<v Speaker 2>sure you're protected from every angle like that.

420
00:19:00.599 --> 00:19:06.160
<v Speaker 1>So, for example, we'd be analyzing firewall rules, testing our

421
00:19:06.200 --> 00:19:12.279
<v Speaker 1>intrusion prevention systems, evaluating access control mechanisms, making sure our

422
00:19:12.319 --> 00:19:17.039
<v Speaker 1>wireless networks are secure, reviewing physical security measure It's a.

423
00:19:17.000 --> 00:19:19.240
<v Speaker 2>Lot, it's a lot, yeah, but it's important.

424
00:19:19.920 --> 00:19:22.480
<v Speaker 1>Okay. So it's a thorough process. But how do we

425
00:19:22.519 --> 00:19:26.799
<v Speaker 1>even know which channels and vectors are relevant to our organization?

426
00:19:27.000 --> 00:19:30.960
<v Speaker 1>I mean, there's so many potential attack vectors out there.

427
00:19:31.039 --> 00:19:34.079
<v Speaker 2>That's where that posture review comes in hand. Remember, we

428
00:19:34.160 --> 00:19:38.400
<v Speaker 2>gathered all that information about the organization, their assets, their environment.

429
00:19:39.039 --> 00:19:41.480
<v Speaker 2>That helps you figure out which channels and vectors you

430
00:19:41.480 --> 00:19:42.480
<v Speaker 2>should be focusing on.

431
00:19:42.559 --> 00:19:45.720
<v Speaker 1>Okay, so it's all connected. The information from the early

432
00:19:45.799 --> 00:19:50.279
<v Speaker 1>stages actually informs the later stages exactly. That's good. The

433
00:19:50.359 --> 00:19:54.319
<v Speaker 1>OSSTMM is really systematic and methodical. It's designed to make

434
00:19:54.319 --> 00:19:57.799
<v Speaker 1>sure that you don't miss anything important thorough Yeah. Okay,

435
00:19:57.960 --> 00:20:01.119
<v Speaker 1>so we've got active detection verification, we've got channel in

436
00:20:01.200 --> 00:20:05.720
<v Speaker 1>vector verification. What comes next in the OSSTM methodology flow.

437
00:20:05.839 --> 00:20:09.599
<v Speaker 2>Next is process verification process verification. Yeah, this is where

438
00:20:09.599 --> 00:20:12.920
<v Speaker 2>you look at the organization's processes and procedures and you're

439
00:20:12.920 --> 00:20:15.079
<v Speaker 2>asking are they actually effective?

440
00:20:15.240 --> 00:20:19.279
<v Speaker 1>So are people actually following the security policies exactly? Do

441
00:20:19.319 --> 00:20:22.200
<v Speaker 1>they know what to do if something bad happens?

442
00:20:22.359 --> 00:20:25.680
<v Speaker 2>You got it? So you're reviewing those policies and procedures.

443
00:20:26.160 --> 00:20:30.240
<v Speaker 2>You're actually watching people seeing how they work. You're interviewing them,

444
00:20:30.400 --> 00:20:33.240
<v Speaker 2>asking them about their understanding of security.

445
00:20:33.279 --> 00:20:35.799
<v Speaker 1>So it's not just about having rules on paper, it's

446
00:20:35.839 --> 00:20:37.559
<v Speaker 1>about security being part of the culture.

447
00:20:37.720 --> 00:20:38.720
<v Speaker 2>It's got to be ingrained.

448
00:20:38.880 --> 00:20:43.039
<v Speaker 1>Yeah. Yeah, But how do you assess something like organizational

449
00:20:43.039 --> 00:20:44.480
<v Speaker 1>culture that seems kind of fuzzy?

450
00:20:44.599 --> 00:20:48.160
<v Speaker 2>It can be. Yeah, but the OSSTMM gives you some guidance.

451
00:20:48.759 --> 00:20:52.880
<v Speaker 2>You look for evidence of security awareness training. Are they

452
00:20:52.880 --> 00:20:56.359
<v Speaker 2>doing incident response drills? Is there a clear way to

453
00:20:56.440 --> 00:20:58.200
<v Speaker 2>report security incidents?

454
00:20:58.480 --> 00:21:02.640
<v Speaker 1>So you're looking for concrete that they're taking security seriously.

455
00:21:02.720 --> 00:21:04.720
<v Speaker 2>Yeah, it's got to be more than just words.

456
00:21:04.640 --> 00:21:05.759
<v Speaker 1>Yeah, to be actions.

457
00:21:05.839 --> 00:21:07.920
<v Speaker 2>Actions speak louder than words, exactly.

458
00:21:08.359 --> 00:21:13.119
<v Speaker 1>Okay. So process verification it's about making sure everyone's.

459
00:21:12.759 --> 00:21:15.039
<v Speaker 2>On the same page, everyone working together. Yeah.

460
00:21:15.079 --> 00:21:18.680
<v Speaker 1>Yeah, what's next in the osstmmflow.

461
00:21:18.920 --> 00:21:21.920
<v Speaker 2>Next up is configuration and training.

462
00:21:21.559 --> 00:21:24.440
<v Speaker 1>Verification, configuration and training Okay.

463
00:21:24.599 --> 00:21:27.480
<v Speaker 2>This is where you look at the organization systems okay,

464
00:21:27.519 --> 00:21:28.680
<v Speaker 2>and their training programs.

465
00:21:28.759 --> 00:21:32.680
<v Speaker 1>So are our systems set up properly? And do people

466
00:21:32.759 --> 00:21:34.039
<v Speaker 1>know what they're doing exactly?

467
00:21:34.079 --> 00:21:38.359
<v Speaker 2>So you're reviewing system settings, you're checking password policies, ok

468
00:21:38.759 --> 00:21:40.799
<v Speaker 2>and you're evaluating those training programs.

469
00:21:40.799 --> 00:21:43.640
<v Speaker 1>So it's making sure that our technical defenses and our

470
00:21:43.720 --> 00:21:46.960
<v Speaker 1>human defenses are both up to par. Got to have both, Okay,

471
00:21:47.640 --> 00:21:50.160
<v Speaker 1>But how do we know what a secure configuration even

472
00:21:50.200 --> 00:21:52.519
<v Speaker 1>looks like? I mean, there are so many different settings

473
00:21:52.559 --> 00:21:54.400
<v Speaker 1>and options and it can.

474
00:21:54.279 --> 00:21:56.920
<v Speaker 2>Be overwhelming, yet it can be That's where the OSTMM

475
00:21:57.319 --> 00:21:58.240
<v Speaker 2>comes in handy again.

476
00:21:58.319 --> 00:21:58.559
<v Speaker 1>Okay.

477
00:21:58.599 --> 00:22:02.559
<v Speaker 2>He gives you specific guide good based on industry best

478
00:22:02.559 --> 00:22:04.759
<v Speaker 2>practices and the needs of your organization.

479
00:22:05.240 --> 00:22:08.759
<v Speaker 1>So it's not just a generic checklist. It's about tailoring

480
00:22:08.799 --> 00:22:10.680
<v Speaker 1>things to your specific situation.

481
00:22:10.960 --> 00:22:11.319
<v Speaker 2>You got it.

482
00:22:11.640 --> 00:22:14.039
<v Speaker 1>Okay, that makes sense, And the same goes for the training,

483
00:22:14.160 --> 00:22:18.640
<v Speaker 1>right Exactly. The OSSTMM encourages organizations to make the training

484
00:22:18.799 --> 00:22:21.440
<v Speaker 1>relevant engaging for the employees.

485
00:22:21.599 --> 00:22:25.799
<v Speaker 2>Yeah, you don't want those boring, sleep inducing training sessions, right.

486
00:22:25.640 --> 00:22:28.640
<v Speaker 1>Because then no one remembers anything exactly. Okay. So we've

487
00:22:28.680 --> 00:22:35.799
<v Speaker 1>got configuration and training verification. What's next in the OSSTMM methodology.

488
00:22:36.519 --> 00:22:39.559
<v Speaker 2>Now we're getting into privileged escalation verification.

489
00:22:39.759 --> 00:22:42.119
<v Speaker 1>Privilege escalation, yep, this.

490
00:22:42.000 --> 00:22:46.680
<v Speaker 2>Is where uss how vulnerable you are to attacks that

491
00:22:46.759 --> 00:22:49.359
<v Speaker 2>try to gain unauthorized privileges.

492
00:22:49.519 --> 00:22:51.920
<v Speaker 1>So making sure attackers can't like level up and get

493
00:22:51.960 --> 00:22:53.839
<v Speaker 1>access to stuff they shouldn't exactly.

494
00:22:54.160 --> 00:22:57.200
<v Speaker 2>Okay, So you're trying to find those vulnerabilities. You're testing

495
00:22:57.240 --> 00:23:01.319
<v Speaker 2>your access controls, you're looking at your monitoring and logging processes.

496
00:23:01.400 --> 00:23:05.000
<v Speaker 1>So it's about being proactive absolutely understanding how attackers might

497
00:23:05.039 --> 00:23:09.559
<v Speaker 1>try to escalate their privileges so we can stop them exactly. Okay,

498
00:23:09.559 --> 00:23:13.400
<v Speaker 1>but how do you even begin to identify those vulnerabilities.

499
00:23:13.960 --> 00:23:16.319
<v Speaker 1>It seems like looking for a needle in a haystack.

500
00:23:16.599 --> 00:23:20.160
<v Speaker 2>It could be tough. Yeah, but the OSSTMM gives you

501
00:23:20.240 --> 00:23:24.480
<v Speaker 2>some pointers okay. It talks about common techniques and vulnerabilities okay,

502
00:23:24.640 --> 00:23:28.400
<v Speaker 2>and it encourages you to use tools like vulnerability scanners, right,

503
00:23:28.640 --> 00:23:29.839
<v Speaker 2>penetration testing, So.

504
00:23:29.839 --> 00:23:32.119
<v Speaker 1>A combination of manual and automated techniques.

505
00:23:32.160 --> 00:23:33.480
<v Speaker 2>You got it. You got to use all the tools

506
00:23:33.480 --> 00:23:34.119
<v Speaker 2>at your disposal.

507
00:23:34.240 --> 00:23:37.240
<v Speaker 1>Okay. And once you've found those vulnerabilities, then you.

508
00:23:37.240 --> 00:23:40.119
<v Speaker 2>Fix them right right, Patch your systems, tighten up those

509
00:23:40.160 --> 00:23:41.079
<v Speaker 2>access controls.

510
00:23:41.160 --> 00:23:43.720
<v Speaker 1>Okay. So you're constantly finding problems and fixing them.

511
00:23:43.839 --> 00:23:45.079
<v Speaker 2>It's an ongoing process.

512
00:23:45.200 --> 00:23:49.119
<v Speaker 1>Okay. So we've got privileged escalation verification. What's next on

513
00:23:49.160 --> 00:23:50.559
<v Speaker 1>the OSSTMM list.

514
00:23:51.079 --> 00:23:53.759
<v Speaker 2>Next is containment and egress verification.

515
00:23:53.960 --> 00:23:55.440
<v Speaker 1>Containment and egress.

516
00:23:55.519 --> 00:23:58.599
<v Speaker 2>This is where you assess your ability to you know,

517
00:23:58.640 --> 00:24:02.640
<v Speaker 2>contain security incident okay, and prevent data from leaking out.

518
00:24:02.920 --> 00:24:05.440
<v Speaker 1>So if an attacker gets in, can we limit the

519
00:24:05.559 --> 00:24:06.759
<v Speaker 1>damage exactly?

520
00:24:06.839 --> 00:24:09.119
<v Speaker 2>Can you stop them from making off with all your

521
00:24:09.160 --> 00:24:09.920
<v Speaker 2>sensitive data?

522
00:24:10.079 --> 00:24:10.400
<v Speaker 1>Okay?

523
00:24:10.640 --> 00:24:14.759
<v Speaker 2>That's crucial it is, So you're testing your incident response plans. Okay,

524
00:24:14.839 --> 00:24:18.039
<v Speaker 2>you're looking at your data laws prevention mechanisms, and you're

525
00:24:18.119 --> 00:24:20.640
<v Speaker 2>checking your network segmentation strategies.

526
00:24:20.880 --> 00:24:24.079
<v Speaker 1>So it's about having a plan in place and making

527
00:24:24.079 --> 00:24:26.359
<v Speaker 1>sure we can protect our valuables.

528
00:24:26.440 --> 00:24:30.240
<v Speaker 2>You got it. Now, what if those controls aren't good enough?

529
00:24:30.640 --> 00:24:31.720
<v Speaker 1>Right? Good point?

530
00:24:31.920 --> 00:24:32.960
<v Speaker 2>What do you do? Yeah?

531
00:24:33.119 --> 00:24:33.559
<v Speaker 1>What then?

532
00:24:33.759 --> 00:24:38.640
<v Speaker 2>The OSSTMM gives you more recommendations okay, best practices for

533
00:24:38.759 --> 00:24:39.880
<v Speaker 2>improving those controls.

534
00:24:39.920 --> 00:24:40.319
<v Speaker 1>Okay.

535
00:24:40.440 --> 00:24:43.559
<v Speaker 2>Maybe you need to develop a more robust incident response

536
00:24:43.640 --> 00:24:48.119
<v Speaker 2>plan okay, or implement data loss prevention solutions, or maybe

537
00:24:48.119 --> 00:24:50.839
<v Speaker 2>you need to strengthen your network segmentation okay.

538
00:24:50.880 --> 00:24:55.119
<v Speaker 1>So you use the findings to drive security improvements exactly.

539
00:24:55.160 --> 00:24:57.759
<v Speaker 1>The OSSTMM is really a cyclical process.

540
00:24:57.920 --> 00:25:01.160
<v Speaker 2>It is you assess, you find weakness, you make improvements,

541
00:25:01.799 --> 00:25:03.759
<v Speaker 2>and then you assess again. You just keep going, you

542
00:25:03.839 --> 00:25:04.240
<v Speaker 2>keep going.

543
00:25:04.440 --> 00:25:07.799
<v Speaker 1>Okay. So we're constantly evaluating, evolving our.

544
00:25:07.720 --> 00:25:09.640
<v Speaker 2>Security posture, always evolving.

545
00:25:09.680 --> 00:25:11.079
<v Speaker 1>Okay, what's next on the list?

546
00:25:11.240 --> 00:25:13.920
<v Speaker 2>All right, Now we're getting into denial of service verification.

547
00:25:14.079 --> 00:25:15.039
<v Speaker 1>Denial of service.

548
00:25:15.599 --> 00:25:17.400
<v Speaker 2>This is where you see how vulnerable you are to

549
00:25:17.440 --> 00:25:20.519
<v Speaker 2>those denial of service attacks d dos.

550
00:25:20.599 --> 00:25:23.359
<v Speaker 1>Yep, those are the ones where they flood a system.

551
00:25:23.039 --> 00:25:25.079
<v Speaker 2>With traffic, they try to overwhelm it.

552
00:25:25.359 --> 00:25:29.519
<v Speaker 1>Yeah, make it unavailable to legitimate users exactly. Okay, those

553
00:25:29.599 --> 00:25:30.839
<v Speaker 1>sound like a nightmare.

554
00:25:30.920 --> 00:25:36.039
<v Speaker 2>It can be really disruptive. Yeah, people can't access websites, applications,

555
00:25:36.079 --> 00:25:37.759
<v Speaker 2>even entire networks can go down.

556
00:25:37.920 --> 00:25:40.759
<v Speaker 1>Okay, So what do you actually do during denial of

557
00:25:40.799 --> 00:25:41.720
<v Speaker 1>service verification?

558
00:25:42.039 --> 00:25:46.160
<v Speaker 2>Well, you're trying to figure out how could someone launch

559
00:25:47.519 --> 00:25:51.039
<v Speaker 2>a d DOS attack against you? Right, You're testing how

560
00:25:51.079 --> 00:25:54.720
<v Speaker 2>resilient your network is, and you're seeing if you have

561
00:25:54.799 --> 00:25:57.039
<v Speaker 2>any d DOAS mitigation strategies in place.

562
00:25:57.119 --> 00:25:59.039
<v Speaker 1>So you're basically trying to figure out how to survive

563
00:25:59.119 --> 00:26:00.160
<v Speaker 1>a DDAs attack.

564
00:26:00.200 --> 00:26:02.440
<v Speaker 2>You got it? Okay, you want to build a network

565
00:26:02.480 --> 00:26:04.680
<v Speaker 2>that can withstand that kind of pressure, sure.

566
00:26:04.759 --> 00:26:08.079
<v Speaker 1>Right, right? Okay, so we've covered denial of service verification.

567
00:26:08.640 --> 00:26:11.319
<v Speaker 1>What's next on the OSTMM agenda.

568
00:26:11.559 --> 00:26:16.960
<v Speaker 2>Next up is business disruption verification Business disruption. This one's

569
00:26:17.039 --> 00:26:20.599
<v Speaker 2>interesting because here you're looking at attacks that go beyond

570
00:26:20.880 --> 00:26:22.440
<v Speaker 2>just technical disruptions.

571
00:26:22.960 --> 00:26:25.759
<v Speaker 1>Okay, So it's not just about taking down a website.

572
00:26:26.240 --> 00:26:30.759
<v Speaker 2>It's about disrupting the organization's ability to function. Wow, So

573
00:26:30.799 --> 00:26:34.599
<v Speaker 2>we're talking about things like ransomware attacks that encrypt your data,

574
00:26:35.160 --> 00:26:39.119
<v Speaker 2>d tos, attacks that cripple your online services, even physical

575
00:26:39.160 --> 00:26:41.160
<v Speaker 2>attacks oh right, damage your facilities.

576
00:26:41.240 --> 00:26:45.480
<v Speaker 1>So these are attacks that really impact the bottom line exactly. Okay,

577
00:26:45.480 --> 00:26:49.839
<v Speaker 1>what kind of tasks are involved in business disruption verification?

578
00:26:50.079 --> 00:26:52.680
<v Speaker 2>Well, first you got to figure out what are the

579
00:26:52.839 --> 00:26:56.839
<v Speaker 2>organization's critical business processes? Okay, what are their most important assets.

580
00:26:57.119 --> 00:26:59.240
<v Speaker 2>Then you think about, okay, what would happen if those

581
00:26:59.240 --> 00:27:01.359
<v Speaker 2>were disrupted? Okay, what's the impact going to be?

582
00:27:01.480 --> 00:27:01.599
<v Speaker 3>Right?

583
00:27:01.680 --> 00:27:04.279
<v Speaker 2>And then you see do they have any plans in

584
00:27:04.319 --> 00:27:05.160
<v Speaker 2>place to recover?

585
00:27:05.359 --> 00:27:09.559
<v Speaker 1>So you're thinking about business continuity, disaster recovery exactly.

586
00:27:09.680 --> 00:27:12.359
<v Speaker 2>You want to make sure the organization can keep running even.

587
00:27:12.200 --> 00:27:16.920
<v Speaker 1>If something bad happens, to be prepared. Okay, So business

588
00:27:16.920 --> 00:27:21.000
<v Speaker 1>disruption verification it's about building resilience, being able to bounce

589
00:27:21.039 --> 00:27:22.119
<v Speaker 1>back from those disruptions.

590
00:27:22.200 --> 00:27:22.599
<v Speaker 2>You got it.

591
00:27:23.119 --> 00:27:27.160
<v Speaker 1>Okay, what's next on the OSSTMM checklist?

592
00:27:27.480 --> 00:27:33.079
<v Speaker 2>All right, now we're getting into social engineering verifications engineer yep,

593
00:27:33.160 --> 00:27:36.400
<v Speaker 2>this is where you assess how vulnerable the organization is

594
00:27:36.400 --> 00:27:38.279
<v Speaker 2>to those sneaky attacks.

595
00:27:37.960 --> 00:27:42.440
<v Speaker 1>Those attacks that prey on human psychology. Exactly, the trickery,

596
00:27:42.759 --> 00:27:43.960
<v Speaker 1>the deception, it's all.

597
00:27:43.920 --> 00:27:47.279
<v Speaker 2>About manipulating people, getting them to do things they shouldn't.

598
00:27:46.839 --> 00:27:49.000
<v Speaker 1>Give up sensitive information or.

599
00:27:48.960 --> 00:27:52.440
<v Speaker 2>Click on a malicious link, right right, social engineering attacks

600
00:27:52.440 --> 00:27:53.480
<v Speaker 2>can be really effective.

601
00:27:53.640 --> 00:27:55.720
<v Speaker 1>Yeah, because people want to be helpful.

602
00:27:55.559 --> 00:27:58.200
<v Speaker 2>Exactly, a trust people and attackers exploit that.

603
00:27:58.440 --> 00:28:02.000
<v Speaker 1>So what do you actually do during social engineering verification?

604
00:28:02.759 --> 00:28:06.960
<v Speaker 2>Well, you might do some simulations see how susceptible employees are, right.

605
00:28:07.039 --> 00:28:09.680
<v Speaker 2>You might even do some penetration testing okay. But it's

606
00:28:09.720 --> 00:28:13.319
<v Speaker 2>also about looking at the training programs, right, are they

607
00:28:13.359 --> 00:28:15.880
<v Speaker 2>actually teaching people about social engineering?

608
00:28:16.039 --> 00:28:16.480
<v Speaker 1>Okay?

609
00:28:16.559 --> 00:28:18.920
<v Speaker 2>And then you look for ways to improve your policies

610
00:28:18.920 --> 00:28:19.599
<v Speaker 2>and procedures.

611
00:28:19.640 --> 00:28:24.039
<v Speaker 1>So it's about understanding the tactics, training people to resist

612
00:28:24.079 --> 00:28:26.440
<v Speaker 1>them exactly, and putting safeguards in place.

613
00:28:26.640 --> 00:28:28.240
<v Speaker 2>I have multiple layers of defense.

614
00:28:28.359 --> 00:28:33.079
<v Speaker 1>Okay. So social engineering verification it's all about building a

615
00:28:33.200 --> 00:28:34.680
<v Speaker 1>security aware culture.

616
00:28:34.759 --> 00:28:35.200
<v Speaker 2>You got it?

617
00:28:35.799 --> 00:28:38.799
<v Speaker 1>Okay, what's next on the OSDMM agenda?

618
00:28:39.000 --> 00:28:43.640
<v Speaker 2>Next up is physical security verification Physical security. Yeah, this

619
00:28:43.720 --> 00:28:45.880
<v Speaker 2>is where you assess those physical controls.

620
00:28:45.960 --> 00:28:50.839
<v Speaker 1>So we're talking locks, fences, cameras, guards.

621
00:28:50.440 --> 00:28:52.680
<v Speaker 2>All that, all of that. Yeah. It's easy to overlook

622
00:28:52.680 --> 00:28:53.920
<v Speaker 2>physical security.

623
00:28:53.519 --> 00:28:57.559
<v Speaker 1>These days, right, Yeah, with everyone focused on cyber but it's.

624
00:28:57.440 --> 00:29:00.000
<v Speaker 2>Still essential, it is. Yeah, you can have the best

625
00:29:00.039 --> 00:29:02.680
<v Speaker 2>cybersecurity in the world. But if someone can just walk

626
00:29:02.720 --> 00:29:06.039
<v Speaker 2>into your building and steal your servers, game over exactly.

627
00:29:06.119 --> 00:29:09.359
<v Speaker 1>Okay, So what kind of tasks are involved in physical

628
00:29:09.440 --> 00:29:10.519
<v Speaker 1>security verification.

629
00:29:11.079 --> 00:29:14.279
<v Speaker 2>You're testing your access control systems, You're looking at your

630
00:29:14.319 --> 00:29:19.559
<v Speaker 2>surveillance coverage, you're assessing your security personnel, and you're reviewing

631
00:29:19.680 --> 00:29:23.880
<v Speaker 2>those environmental controls and disaster preparedness plans.

632
00:29:24.079 --> 00:29:26.720
<v Speaker 1>So you're making sure those physical defenses are just as

633
00:29:26.720 --> 00:29:28.400
<v Speaker 1>strong as your digital defenses.

634
00:29:28.559 --> 00:29:29.680
<v Speaker 2>Got to have a balanced approach.

635
00:29:29.759 --> 00:29:33.920
<v Speaker 1>Okay, makes sense. So we've covered physical security verification. What's

636
00:29:34.079 --> 00:29:37.440
<v Speaker 1>next on the OSSTMM roadmap.

637
00:29:38.240 --> 00:29:40.799
<v Speaker 2>Now we're moving on to wireless security verification.

638
00:29:41.039 --> 00:29:42.039
<v Speaker 1>Wireless security.

639
00:29:42.079 --> 00:29:44.000
<v Speaker 2>This is where you assess the security of all those

640
00:29:44.000 --> 00:29:45.440
<v Speaker 2>wireless networks.

641
00:29:45.160 --> 00:29:49.480
<v Speaker 1>Wi Fi, Bluetooth, RFID, all that good stuff, all of it. Okay,

642
00:29:49.480 --> 00:29:52.640
<v Speaker 1>wireless security is crucial these days, absolutely, I mean everyone's

643
00:29:52.640 --> 00:29:54.319
<v Speaker 1>connected wirelessly, exactly.

644
00:29:54.400 --> 00:29:56.599
<v Speaker 2>So what do we do during wireless security verification?

645
00:29:56.799 --> 00:29:57.480
<v Speaker 1>What do we do?

646
00:29:57.519 --> 00:30:00.359
<v Speaker 2>We test those security settings. We try to break into

647
00:30:00.400 --> 00:30:01.440
<v Speaker 2>those networks.

648
00:30:01.119 --> 00:30:02.799
<v Speaker 1>Right, We try to break into those networks.

649
00:30:02.519 --> 00:30:05.400
<v Speaker 2>Yectly, quite a reagular. We see how strong those encryption

650
00:30:05.480 --> 00:30:08.839
<v Speaker 2>protocols are, and we check if there are any intrusion

651
00:30:08.880 --> 00:30:10.759
<v Speaker 2>detection or prevention systems in place.

652
00:30:11.240 --> 00:30:14.079
<v Speaker 1>So we're basically trying to find any weaknesses in our

653
00:30:14.160 --> 00:30:15.319
<v Speaker 1>wireless defenses.

654
00:30:15.440 --> 00:30:16.759
<v Speaker 2>Exactly. You got to be proactive.

655
00:30:16.880 --> 00:30:20.960
<v Speaker 1>Yeah, Okay, Wireless security verification, that's all about building a

656
00:30:20.960 --> 00:30:22.960
<v Speaker 1>secure wireless environment.

657
00:30:22.599 --> 00:30:24.720
<v Speaker 2>Keeping your data and your devices safe.

658
00:30:24.799 --> 00:30:27.680
<v Speaker 1>All right. What's next on the OSSTMM agenda.

659
00:30:27.960 --> 00:30:31.039
<v Speaker 2>Next is telecommunications security verification.

660
00:30:31.200 --> 00:30:32.599
<v Speaker 1>Telecommunications security.

661
00:30:32.759 --> 00:30:35.960
<v Speaker 2>This is all about those traditional telecommunication.

662
00:30:35.240 --> 00:30:39.119
<v Speaker 1>Systems, so like phone lines, voicemail, fax machines, all that.

663
00:30:39.480 --> 00:30:41.519
<v Speaker 2>All of that. Yeah, those systems can.

664
00:30:41.440 --> 00:30:44.559
<v Speaker 1>Still be vulnerable, right, Yeah, we tend to forget about those.

665
00:30:44.799 --> 00:30:47.160
<v Speaker 2>We focus so much on the cyber stuff. Yeah, that

666
00:30:47.200 --> 00:30:49.240
<v Speaker 2>we forget about the old school stuff, but it's still

667
00:30:49.240 --> 00:30:55.319
<v Speaker 2>important absolutely. So during telecommunications security verification, you might test

668
00:30:55.400 --> 00:30:58.279
<v Speaker 2>the security of your voicemail systems. Okay, you might try

669
00:30:58.279 --> 00:31:02.240
<v Speaker 2>to eavesdrop on phone com wow. You might check the

670
00:31:02.240 --> 00:31:03.839
<v Speaker 2>physical security of your equipment.

671
00:31:03.960 --> 00:31:06.640
<v Speaker 1>So it's about making sure our phone calls are private

672
00:31:07.240 --> 00:31:09.400
<v Speaker 1>and our voicemail messages are secure.

673
00:31:09.720 --> 00:31:13.279
<v Speaker 2>Exactly. You don't want anyone snooping on your conversations, right right.

674
00:31:13.480 --> 00:31:18.839
<v Speaker 1>Okay, so we've covered telecommunications security verification. What's Next on

675
00:31:18.920 --> 00:31:21.079
<v Speaker 1>the OSSTMM checklist.

676
00:31:21.519 --> 00:31:25.920
<v Speaker 2>All right, now we're getting to data networks security verification.

677
00:31:26.079 --> 00:31:28.559
<v Speaker 1>Data networks okay, that's the big one. Yeah, the heart

678
00:31:28.640 --> 00:31:29.640
<v Speaker 1>of cybersecurity.

679
00:31:29.680 --> 00:31:32.200
<v Speaker 2>This is where you're assessing the security of your networks

680
00:31:32.200 --> 00:31:32.920
<v Speaker 2>and your systems.

681
00:31:32.920 --> 00:31:37.440
<v Speaker 1>So protecting our computers, our servers, our data, whole nine yards.

682
00:31:37.200 --> 00:31:38.519
<v Speaker 2>The whole nine yards. Yeah, all right.

683
00:31:38.759 --> 00:31:42.799
<v Speaker 1>What kind of tasks are involved in data networks security verification.

684
00:31:42.960 --> 00:31:48.240
<v Speaker 2>Oh, we're talking penetration testing, okay, vulnerability scanning, configuration reviews,

685
00:31:48.279 --> 00:31:49.599
<v Speaker 2>security log analysis.

686
00:31:49.640 --> 00:31:51.000
<v Speaker 1>Wow, it's a lot, it is.

687
00:31:51.079 --> 00:31:53.559
<v Speaker 2>Yeah, but it's all about finding those weaknesses before the.

688
00:31:53.480 --> 00:31:58.039
<v Speaker 1>Attackers do exactly. Okay. So data networks security verification, it's

689
00:31:58.039 --> 00:32:01.000
<v Speaker 1>about building a really strong network infrastructure, you.

690
00:32:01.079 --> 00:32:04.079
<v Speaker 2>Got it, protecting your data from all those cyber threats.

691
00:32:04.319 --> 00:32:08.920
<v Speaker 1>Okay, so we've covered data networks security verification. What's next

692
00:32:08.960 --> 00:32:10.720
<v Speaker 1>on the OSSTMM agenda?

693
00:32:10.880 --> 00:32:13.160
<v Speaker 2>All right, Next up is compliance verification.

694
00:32:13.720 --> 00:32:14.480
<v Speaker 1>Compliance.

695
00:32:14.680 --> 00:32:17.720
<v Speaker 2>This is where you make sure you're following all the rules, okay,

696
00:32:17.920 --> 00:32:20.920
<v Speaker 2>meeting those legal and regulatory obligations.

697
00:32:20.319 --> 00:32:22.759
<v Speaker 1>So ticking all the right boxes. It's making sure we're

698
00:32:22.759 --> 00:32:25.079
<v Speaker 1>not going to get in trouble with the authorities. Okay,

699
00:32:25.119 --> 00:32:27.519
<v Speaker 1>that makes sense. But how do we even know which

700
00:32:27.559 --> 00:32:30.839
<v Speaker 1>compliance requirements apply to us? I mean, there's so many

701
00:32:31.000 --> 00:32:33.519
<v Speaker 1>laws and regulations and standards out there.

702
00:32:33.640 --> 00:32:38.279
<v Speaker 2>It can be overwhelming. Yeah, but THESTMM gives you some guidance.

703
00:32:38.480 --> 00:32:38.720
<v Speaker 1>Okay.

704
00:32:39.000 --> 00:32:42.119
<v Speaker 2>It helps you figure out which rules apply to your

705
00:32:42.160 --> 00:32:43.319
<v Speaker 2>specific situation.

706
00:32:43.759 --> 00:32:47.039
<v Speaker 1>Okay, So it's about doing our research making sure we're

707
00:32:47.079 --> 00:32:48.799
<v Speaker 1>following the right rules exactly.

708
00:32:48.960 --> 00:32:51.480
<v Speaker 2>Compliance is an important part of security. Okay.

709
00:32:51.680 --> 00:32:54.920
<v Speaker 1>So we've covered compliance verification. What's the final step in

710
00:32:54.960 --> 00:32:57.400
<v Speaker 1>the OSSTMM methodology flow.

711
00:32:57.599 --> 00:33:02.599
<v Speaker 2>The final step is the survey, alert and log review.

712
00:33:02.720 --> 00:33:04.880
<v Speaker 1>Okay, so it's like the wrap up phase exactly.

713
00:33:04.960 --> 00:33:07.000
<v Speaker 2>Exactly. This is where you look at all the findings

714
00:33:07.039 --> 00:33:10.039
<v Speaker 2>from your assessment, you analyze the results, and you come

715
00:33:10.119 --> 00:33:12.440
<v Speaker 2>up with your recommendations for improvement.

716
00:33:12.640 --> 00:33:15.359
<v Speaker 1>So we're putting all the pieces together, making sense of

717
00:33:15.359 --> 00:33:16.079
<v Speaker 1>the big picture.

718
00:33:16.240 --> 00:33:19.279
<v Speaker 2>Exactly. This is where you turn all that data into action.

719
00:33:19.799 --> 00:33:22.759
<v Speaker 1>Okay, that makes sense. But what kind of tasks are

720
00:33:22.799 --> 00:33:24.599
<v Speaker 1>involved in this final review?

721
00:33:24.759 --> 00:33:28.039
<v Speaker 2>Well, you're reviewing all the findings from those different modules, right,

722
00:33:28.160 --> 00:33:31.720
<v Speaker 2>You're looking at the security logs, the incident reports. You're

723
00:33:31.720 --> 00:33:34.400
<v Speaker 2>trying to find any gaps or weaknesses that you might

724
00:33:34.440 --> 00:33:36.920
<v Speaker 2>have missed, and then you come up with a list

725
00:33:36.920 --> 00:33:41.119
<v Speaker 2>of recommendations, okay, and you prioritize those recommendations so.

726
00:33:41.119 --> 00:33:43.680
<v Speaker 1>If we find a lot of vulnerabilities, we don't have

727
00:33:43.720 --> 00:33:45.079
<v Speaker 1>to try to fix them all at once.

728
00:33:45.279 --> 00:33:47.599
<v Speaker 2>Exactly. You focus on the most critical ones first.

729
00:33:47.599 --> 00:33:49.799
<v Speaker 1>Okay, that makes sense. So it's about focusing on the

730
00:33:49.839 --> 00:33:53.079
<v Speaker 1>biggest risks and then working our way down the list.

731
00:33:53.319 --> 00:33:57.200
<v Speaker 2>You got it. And remember security is an ongoing process.

732
00:33:57.400 --> 00:33:58.880
<v Speaker 1>Yeah, it's not a one time fix.

733
00:33:59.000 --> 00:34:00.799
<v Speaker 2>It's a journey, right right.

734
00:34:00.839 --> 00:34:07.400
<v Speaker 1>We're constantly assessing, identifying weaknesses, making improvements, and then assessing again.

735
00:34:07.480 --> 00:34:10.199
<v Speaker 1>It's a cycle, a cycle of continuous improvement.

736
00:34:10.480 --> 00:34:11.039
<v Speaker 2>Exactly.

737
00:34:11.199 --> 00:34:14.599
<v Speaker 1>This has been incredible. This deep dive into the OSSTMLS

738
00:34:14.639 --> 00:34:17.199
<v Speaker 1>a lot to take in, yeah, it is, but it's

739
00:34:17.239 --> 00:34:20.280
<v Speaker 1>been so insightful. It's really given me a whole new

740
00:34:20.360 --> 00:34:24.119
<v Speaker 1>understanding of how security works. That's the goal, yeah, and

741
00:34:24.159 --> 00:34:27.679
<v Speaker 1>a framework for actually managing security in a smart way.

742
00:34:27.800 --> 00:34:30.239
<v Speaker 2>It's about being strategic, right right.

743
00:34:30.800 --> 00:34:32.440
<v Speaker 1>And you know one thing that keeps coming back to

744
00:34:32.519 --> 00:34:36.360
<v Speaker 1>me is this idea of the movie's.

745
00:34:36.079 --> 00:34:37.480
<v Speaker 2>Defense, the defense.

746
00:34:37.559 --> 00:34:41.480
<v Speaker 1>Yeah, you described it as a security perimeter with no

747
00:34:41.719 --> 00:34:45.400
<v Speaker 1>inside or outside, right, which honestly, sounded kind of mind

748
00:34:45.440 --> 00:34:46.239
<v Speaker 1>blowing at first.

749
00:34:46.320 --> 00:34:47.880
<v Speaker 2>It's a different way of thinking about things.

750
00:34:48.119 --> 00:34:50.559
<v Speaker 1>Yeah, it is. Can you break that down a bit

751
00:34:50.599 --> 00:34:52.920
<v Speaker 1>further from me, How does that actually work in practice?

752
00:34:53.159 --> 00:34:57.400
<v Speaker 2>So the Movie's Defense is really about recognizing that the

753
00:34:57.599 --> 00:35:00.519
<v Speaker 2>old way of thinking about security, Okay, with that hard

754
00:35:00.519 --> 00:35:03.400
<v Speaker 2>perimeter right the castle walls, Yeah, it just doesn't work anymore.

755
00:35:03.519 --> 00:35:04.840
<v Speaker 1>Yeah, no more motes, No more motes.

756
00:35:05.239 --> 00:35:08.159
<v Speaker 2>We're living in a world where information is constantly flowing.

757
00:35:08.000 --> 00:35:10.239
<v Speaker 1>Right across boundaries exactly.

758
00:35:10.400 --> 00:35:13.960
<v Speaker 2>You're accessing data in the cloud, you're connecting to public

759
00:35:14.000 --> 00:35:17.440
<v Speaker 2>Wi Fi, you're sharing information across all these different devices.

760
00:35:17.480 --> 00:35:20.159
<v Speaker 1>So there's no clear line to defend anymore exactly.

761
00:35:20.480 --> 00:35:24.079
<v Speaker 2>So the movie is Defense is about shifting from that static,

762
00:35:24.679 --> 00:35:28.719
<v Speaker 2>perimeter based approach to something more dynamic, more fluid.

763
00:35:29.079 --> 00:35:32.000
<v Speaker 1>So instead of trying to build an impenetrable.

764
00:35:31.320 --> 00:35:34.000
<v Speaker 2>Wall, which is impossible.

765
00:35:33.440 --> 00:35:35.360
<v Speaker 1>Yeah, you can't keep everything, you can't.

766
00:35:35.159 --> 00:35:38.360
<v Speaker 2>The Movie's Defense is about defense in depth. Defense in

767
00:35:38.400 --> 00:35:43.159
<v Speaker 2>depth oka distributing those security controls across multiple layers.

768
00:35:43.199 --> 00:35:47.800
<v Speaker 1>So it's about being flexible, resilient, being able to adapt.

769
00:35:48.000 --> 00:35:51.599
<v Speaker 2>The threat landscape is always changing, so your security.

770
00:35:51.119 --> 00:35:54.480
<v Speaker 1>Has to adapt to So it's not about preventing breaches altogether.

771
00:35:54.639 --> 00:35:57.599
<v Speaker 2>You can't prevent everything. Yeah, it's about minimizing the impact,

772
00:35:58.199 --> 00:36:00.519
<v Speaker 2>containing the damage, recovery quickly.

773
00:36:00.599 --> 00:36:02.639
<v Speaker 1>Okay. So it ties back to what we were talking

774
00:36:02.679 --> 00:36:08.480
<v Speaker 1>about earlier, understanding our trusts, managing risk, not eliminating it.

775
00:36:08.480 --> 00:36:10.199
<v Speaker 2>It's exactly, you got to be smart about it.

776
00:36:10.880 --> 00:36:14.079
<v Speaker 1>Okay. This is really making me rethink my whole approach

777
00:36:14.159 --> 00:36:14.840
<v Speaker 1>to security.

778
00:36:15.119 --> 00:36:16.960
<v Speaker 2>It's a different way of thinking about things, it is.

779
00:36:17.119 --> 00:36:20.079
<v Speaker 1>Yeah, you know, you mentioned in my notes that I

780
00:36:20.159 --> 00:36:23.000
<v Speaker 1>was worried about mention a specific concern from the listener's

781
00:36:23.039 --> 00:36:25.480
<v Speaker 1>source material that relates to the Mobius.

782
00:36:25.199 --> 00:36:28.760
<v Speaker 2>Defense, right, and the movie's defense would say, Okay, don't

783
00:36:28.800 --> 00:36:32.400
<v Speaker 2>try to prevent that specific threat. Okay, think about how

784
00:36:32.400 --> 00:36:35.840
<v Speaker 2>you can build a more resilient system, Okay, a system

785
00:36:35.840 --> 00:36:36.320
<v Speaker 2>that can.

786
00:36:36.280 --> 00:36:40.199
<v Speaker 1>Adapt, right, so even if that happens, we can bounce

787
00:36:40.280 --> 00:36:43.800
<v Speaker 1>back exactly. Okay, this is giving me a lot to

788
00:36:43.840 --> 00:36:46.639
<v Speaker 1>think about. I'm starting to see how the OSSTMM is

789
00:36:46.679 --> 00:36:47.280
<v Speaker 1>not just a.

790
00:36:47.239 --> 00:36:49.199
<v Speaker 2>Set of rules. It's more than that.

791
00:36:49.519 --> 00:36:53.679
<v Speaker 1>Yeah, it's a way of thinking about security. It's a framework, right,

792
00:36:53.800 --> 00:36:56.800
<v Speaker 1>a framework for developing a smarter, more nuanced approach.

793
00:36:56.920 --> 00:36:57.480
<v Speaker 2>You got it.

794
00:36:57.599 --> 00:37:00.800
<v Speaker 1>But honestly, it's a bit daunting, I get it. Where

795
00:37:00.800 --> 00:37:01.599
<v Speaker 1>do I even begin?

796
00:37:02.000 --> 00:37:04.599
<v Speaker 2>Well, the good news is the OSSTMM is practical.

797
00:37:04.880 --> 00:37:05.239
<v Speaker 1>Okay.

798
00:37:05.360 --> 00:37:08.960
<v Speaker 2>It gives you a step by step process for assessing

799
00:37:09.039 --> 00:37:12.480
<v Speaker 2>your security, finding those vulnerabilities, and fixing them. And you

800
00:37:12.519 --> 00:37:15.159
<v Speaker 2>don't have to do it all at once. Start with

801
00:37:15.199 --> 00:37:17.719
<v Speaker 2>the areas that are most important to you, Okay, build

802
00:37:17.760 --> 00:37:18.199
<v Speaker 2>from there.

803
00:37:18.280 --> 00:37:21.559
<v Speaker 1>So take it one step at a time, exactly, prioritize

804
00:37:21.599 --> 00:37:24.159
<v Speaker 1>the risks. Don't be afraid to ask for help.

805
00:37:24.280 --> 00:37:25.559
<v Speaker 2>There are resources out there.

806
00:37:25.559 --> 00:37:26.840
<v Speaker 1>Okay, that sounds manageable.

807
00:37:27.480 --> 00:37:27.840
<v Speaker 2>It is.

808
00:37:28.119 --> 00:37:30.320
<v Speaker 1>Yeah, But you know one thing that really sticks with

809
00:37:30.400 --> 00:37:33.519
<v Speaker 1>me is this idea that security is a journey, not

810
00:37:33.639 --> 00:37:34.440
<v Speaker 1>a destination.

811
00:37:34.920 --> 00:37:36.159
<v Speaker 2>It's an ongoing process.

812
00:37:36.320 --> 00:37:38.360
<v Speaker 1>Yeah, it's something we need to be thinking about all

813
00:37:38.400 --> 00:37:41.039
<v Speaker 1>the time. How do we stay ahead of the curve

814
00:37:41.119 --> 00:37:43.280
<v Speaker 1>when the threats are constantly changing.

815
00:37:43.920 --> 00:37:46.280
<v Speaker 2>That's the challenge it is, yeah, but it's also what

816
00:37:46.400 --> 00:37:50.320
<v Speaker 2>makes it so interesting. Right. The OSSTMM is all about

817
00:37:50.320 --> 00:37:53.039
<v Speaker 2>continuous learning, continuous improvement.

818
00:37:53.199 --> 00:37:56.280
<v Speaker 1>So you've got to stay informed about new threats. Yeah,

819
00:37:56.400 --> 00:37:57.480
<v Speaker 1>new vulnerabilities.

820
00:37:57.519 --> 00:38:01.320
<v Speaker 2>You gotta be curious, okay, try new things, challenge your assumption.

821
00:38:01.480 --> 00:38:05.960
<v Speaker 1>So it's about being proactive, curious and adaptable, embracing the

822
00:38:05.960 --> 00:38:08.039
<v Speaker 1>fact that security never stands still.

823
00:38:08.079 --> 00:38:08.920
<v Speaker 2>It's always evolving.

824
00:38:09.119 --> 00:38:13.000
<v Speaker 1>This has been a fantastic deep dive into the OSSTMM.

825
00:38:13.320 --> 00:38:13.840
<v Speaker 2>It has.

826
00:38:13.880 --> 00:38:16.440
<v Speaker 1>It's given me so much to think about and a

827
00:38:16.480 --> 00:38:18.280
<v Speaker 1>whole new way of looking at security.

828
00:38:18.400 --> 00:38:19.239
<v Speaker 2>I'm glad to hear that.

829
00:38:19.400 --> 00:38:24.360
<v Speaker 1>Yeah, it's not about fear or paranoia. It's about understanding

830
00:38:24.400 --> 00:38:27.639
<v Speaker 1>the risks, taking action, and working together.

831
00:38:27.840 --> 00:38:29.639
<v Speaker 2>We're all in this together exactly.

832
00:38:30.199 --> 00:38:33.679
<v Speaker 1>Thanks for guiding me through this exploration of the OSSTMM.

833
00:38:33.719 --> 00:38:34.639
<v Speaker 2>It's good my pleasure.

834
00:38:34.960 --> 00:38:37.440
<v Speaker 1>I feel like I've gained a valuable new set of

835
00:38:37.480 --> 00:38:40.840
<v Speaker 1>tools and perspectives. Excellent, And to our listeners, we encourage

836
00:38:40.840 --> 00:38:44.119
<v Speaker 1>you to check out the OSSTMM. Yeah, see how its

837
00:38:44.159 --> 00:38:48.119
<v Speaker 1>principles can help you navigate this crazy world of security.

838
00:38:48.199 --> 00:38:49.199
<v Speaker 2>It's a great resource.

839
00:38:49.360 --> 00:38:50.800
<v Speaker 1>Remember, knowledge is power.

840
00:38:51.079 --> 00:38:51.400
<v Speaker 2>It is.

841
00:38:51.480 --> 00:38:54.760
<v Speaker 1>The more you understand the threats, the better decisions you

842
00:38:54.800 --> 00:38:57.639
<v Speaker 1>can make. Absolutely, and together we can build a more

843
00:38:57.639 --> 00:39:00.880
<v Speaker 1>secure future. That's the goal for ourselves in our communities.

844
00:39:01.159 --> 00:39:03.079
<v Speaker 2>I think that's a great place to wrap things up.

845
00:39:03.239 --> 00:39:04.199
<v Speaker 1>Yeah, I think so too.
