1
00:00:16,200 --> 00:00:18,800
This is the identity at the 
center podcast. 

2
00:00:19,000 --> 00:00:22,200
This is a show that talks about 
identity and access management 

3
00:00:22,200 --> 00:00:24,600
and making sure you know who has
access to what? 

4
00:00:25,000 --> 00:00:33,300
Let's get started. 
Welcome to the identity of the 

5
00:00:33,308 --> 00:00:35,500
center podcast I'm Jeff and 
that's Jim. 

6
00:00:35,500 --> 00:00:37,700
Hey Jim hey Jeff. 
How's it going pretty. 

7
00:00:37,700 --> 00:00:41,400
Good yourself, good. 
I've got a Confession to make so

8
00:00:41,800 --> 00:00:42,600
or lunch? 
Yeah. 

9
00:00:42,600 --> 00:00:47,200
For lunch today, had buffalo 
cauliflower and I liked it 

10
00:00:47,200 --> 00:00:50,100
Buffalo college. 
So is that just cauliflower with

11
00:00:50,100 --> 00:00:54,300
like wing sauce on it basically?
Well, there was a breading shell

12
00:00:54,500 --> 00:01:00,500
and it was quite wonderful. 
And, you know, I mean, if I ever

13
00:01:00,700 --> 00:01:04,900
did become a vegan, that would 
definitely be either. 

14
00:01:04,900 --> 00:01:07,300
Use it everyday for every meal. 
You know, we have a restaurant 

15
00:01:07,300 --> 00:01:10,100
around here that does bang bang,
cauliflower, which is Basically 

16
00:01:10,100 --> 00:01:13,000
the same thing. 
It's like lightly breaded 

17
00:01:13,000 --> 00:01:15,600
cauliflower with basically wing 
sauce on it, but I didn't have 

18
00:01:15,600 --> 00:01:19,200
that for lunch. 
I had a deconstructed chicken 

19
00:01:19,200 --> 00:01:23,100
pot, pie, courtesy of my wife 
and the leftovers that we had 

20
00:01:23,100 --> 00:01:25,300
from last night, which was 
absolutely fantastic. 

21
00:01:25,300 --> 00:01:28,300
Yeah, well, my meal want to show
that you care about you. 

22
00:01:28,300 --> 00:01:33,200
If anybody's out there is vegan 
or playing to go vegan, you can 

23
00:01:33,200 --> 00:01:36,300
do it in an unhealthy fashion. 
If you'd like, yeah, you can 

24
00:01:36,300 --> 00:01:37,400
deep fry. 
Anything is what? 

25
00:01:37,400 --> 00:01:38,800
I've what I've come to 
understand. 

26
00:01:38,800 --> 00:01:39,700
You know, the deep-fried, 
Snickers. 

27
00:01:39,800 --> 00:01:43,700
Hers Oreos, deep fried green. 
Beans are really good actually. 

28
00:01:43,700 --> 00:01:47,900
So yeah, you can make anything 
you want as healthy, or as 

29
00:01:47,900 --> 00:01:50,300
unhealthy as you want, we're 
recording on hump day. 

30
00:01:50,300 --> 00:01:53,200
So you have to find some way to 
kind of get over the hump. 

31
00:01:53,200 --> 00:01:56,800
And that was it for me. 
Well, not only is it a hump day?

32
00:01:56,800 --> 00:01:59,800
It's, you know towards the end 
of the year I'm planning on 

33
00:01:59,800 --> 00:02:03,200
hitting on vacation, hopefully, 
sometimes towards the end of 

34
00:02:03,200 --> 00:02:06,400
next week. 
It's going to be our last show 

35
00:02:06,400 --> 00:02:09,100
of the year or for the podcast 
itself. 

36
00:02:09,100 --> 00:02:12,800
So You know, hopefully, we leave
on a good note here, I'm sure we

37
00:02:12,800 --> 00:02:14,400
will. 
We had some, some great episodes

38
00:02:14,400 --> 00:02:15,700
throughout the year and this 
will be. 

39
00:02:15,700 --> 00:02:18,800
This will be it for us in 2020 
and will see you guys again in 

40
00:02:18,800 --> 00:02:21,800
2021. 
But before we get too far along,

41
00:02:21,800 --> 00:02:24,000
because I don't think anyone 
wants to hear about our lunch 

42
00:02:24,100 --> 00:02:29,600
habits and our culinary desires.
Why don't we talk a little bit 

43
00:02:29,600 --> 00:02:31,700
about privileged? 
Access management, are you cool 

44
00:02:31,700 --> 00:02:34,200
with that if that fits into the 
theme of this being an? 

45
00:02:34,200 --> 00:02:38,300
I am podcast so sure. 
Well you know we try so to help 

46
00:02:38,300 --> 00:02:40,900
us with that conversation. 
We do Have a guess we've got 

47
00:02:40,900 --> 00:02:43,900
Katie mccroskey, she's the 
director of Knowledge Management

48
00:02:43,900 --> 00:02:46,600
and training at psychotic. 
Welcome to the show. 

49
00:02:46,600 --> 00:02:49,300
Katie, thank you for having me. 
What did you have for lunch? 

50
00:02:49,700 --> 00:02:52,500
I had a breakfast sandwich 
actually sausage or bacon. 

51
00:02:52,900 --> 00:02:56,100
Bacon American cheese, not 
chatter, of course. 

52
00:02:56,100 --> 00:02:57,800
Yeah. 
All right, I guess you could 

53
00:02:57,800 --> 00:03:01,100
stick around, I can eat anytime 
of day. 

54
00:03:02,300 --> 00:03:06,500
So with with, with our lunch out
of the way, why don't we talk 

55
00:03:06,500 --> 00:03:09,400
about your background? 
Katie before we get into some 

56
00:03:09,500 --> 00:03:11,300
some Sexy. 
Pam talk. 

57
00:03:11,400 --> 00:03:13,900
Maybe we can talk through what 
your background is and you I am 

58
00:03:13,900 --> 00:03:16,100
space. 
How did you get into? 

59
00:03:16,100 --> 00:03:18,500
I am? 
Is it something that you chose 

60
00:03:18,500 --> 00:03:23,700
or did it choose you? 
I am chose me actually I call 

61
00:03:23,700 --> 00:03:25,100
it. 
The Luck of the Irish. 

62
00:03:25,500 --> 00:03:30,600
I stumbled into it. 
I'm actually an MBA by trade. 

63
00:03:30,600 --> 00:03:37,000
I applied to join a small 
psychotic startup almost 12 

64
00:03:37,000 --> 00:03:41,000
years ago at the time we were 
actually A focused on helping 

65
00:03:41,000 --> 00:03:45,800
organizations build software. 
So there was an agile focus and 

66
00:03:45,800 --> 00:03:49,500
a Consulting practice. 
We did have secret server as a 

67
00:03:49,508 --> 00:03:51,600
product and a few other 
products. 

68
00:03:51,600 --> 00:03:54,900
But at that time it was more of 
an Ops tool. 

69
00:03:55,600 --> 00:03:57,900
Interestingly enough secret 
server in some of our other 

70
00:03:57,900 --> 00:04:01,600
products were born from our own 
needs and as the product 

71
00:04:01,600 --> 00:04:05,900
capability is matured and the 
organization changed became more

72
00:04:05,900 --> 00:04:09,600
and more of a focus for identity
and access management. 

73
00:04:09,800 --> 00:04:14,800
And for me being an MBA I joined
psychotic not knowing what a 

74
00:04:14,800 --> 00:04:19,000
server was. 
So I really needed to teach 

75
00:04:19,000 --> 00:04:24,400
myself and understand the market
and all the different new tech 

76
00:04:24,400 --> 00:04:27,800
terms and Concepts. 
I was learning and being 

77
00:04:27,800 --> 00:04:30,600
introduced to working at a 
security software company. 

78
00:04:30,600 --> 00:04:35,000
So yes, I very much stumbled 
into identity and access. 

79
00:04:35,200 --> 00:04:39,100
That, that story is almost hard 
to believe because Katie we 

80
00:04:40,600 --> 00:04:45,400
Interacted with you on on a 
couple of calls and you're very 

81
00:04:45,400 --> 00:04:50,900
technical now, very capable and 
I just assume that you're 

82
00:04:51,200 --> 00:04:54,300
installing servers when you were
like six years old, or some 

83
00:04:54,300 --> 00:04:59,500
things but interesting, my, you 
know, when I first heard about 

84
00:04:59,500 --> 00:05:02,500
psychotic and found out, they 
had a product called Secret 

85
00:05:02,500 --> 00:05:04,000
Service. 
Like, oh, that's so funny. 

86
00:05:04,000 --> 00:05:06,900
I used to work with a product 
called secret server and it was 

87
00:05:06,900 --> 00:05:08,500
awesome. 
Well, it turned out, it was the 

88
00:05:08,500 --> 00:05:13,600
same product and You know, I was
using it to manage Windows 

89
00:05:13,600 --> 00:05:15,600
service accounts, way back in 
the day. 

90
00:05:15,600 --> 00:05:17,000
I couldn't give you an exact 
year. 

91
00:05:17,000 --> 00:05:22,900
But yeah, that's how that that's
really from that, that product 

92
00:05:22,900 --> 00:05:27,200
which was, you know, price try 
just for like a, you know, a 

93
00:05:27,200 --> 00:05:30,100
specific use case. 
It's really become kind of a 

94
00:05:30,300 --> 00:05:33,600
Enterprise, Pam solution, not 
any kind of commercial for 

95
00:05:33,600 --> 00:05:37,100
psychotic, but that just was my 
own personal experience with 

96
00:05:37,100 --> 00:05:39,800
secret server. 
So, anyway, Katie one of The 

97
00:05:39,800 --> 00:05:43,400
things that I thought we could, 
maybe kind of talk about today 

98
00:05:43,400 --> 00:05:47,800
is more or less of like a 
privileged access management 101

99
00:05:48,600 --> 00:05:52,000
for those of those of our 
listeners who are, you know, not

100
00:05:52,000 --> 00:05:56,500
steeped in privileged access 
management, maybe start off with

101
00:05:56,500 --> 00:05:59,200
kind of some of the 
bread-and-butter use cases like 

102
00:05:59,400 --> 00:06:03,400
shared account management, 
service accounts session 

103
00:06:03,400 --> 00:06:07,200
monitoring and you know session 
elevations. 

104
00:06:07,200 --> 00:06:09,500
So maybe kind of talk us 
through. 

105
00:06:09,800 --> 00:06:14,700
From the basic bread and butter 
101 stuff for privileged access 

106
00:06:14,700 --> 00:06:16,100
management. 
Sure. 

107
00:06:16,600 --> 00:06:20,800
I think a lot of it often starts
with vaulting, right? 

108
00:06:20,800 --> 00:06:25,500
Just kind of a secure place to 
store and then of course, 

109
00:06:25,500 --> 00:06:28,600
delegate access ought to access 
privileged access. 

110
00:06:29,100 --> 00:06:32,900
I think traditionally, folks, 
look at the infrastructure, you 

111
00:06:32,900 --> 00:06:36,100
look at local administrative 
privileges domain privileges 

112
00:06:36,500 --> 00:06:38,900
shared accounts, service 
accounts. 

113
00:06:39,700 --> 00:06:43,100
Any type of database networking 
infrastructure accounts that 

114
00:06:43,100 --> 00:06:47,600
they want for their controls on 
now, it doesn't always have to 

115
00:06:47,600 --> 00:06:53,300
be very complex things. 
Sometimes I preach about simple,

116
00:06:53,300 --> 00:06:56,100
security steps. 
I can exponentially increase in 

117
00:06:56,100 --> 00:06:58,600
organization's overall security 
posture. 

118
00:06:58,800 --> 00:07:00,900
So for example, a password, 
right? 

119
00:07:00,900 --> 00:07:04,500
Having a long password. 
So 50 characters, 100 

120
00:07:04,500 --> 00:07:09,400
characters, completely random 
and rotating that password every

121
00:07:09,700 --> 00:07:13,700
Week every day, every hour, 
things like that are really the 

122
00:07:13,700 --> 00:07:18,100
core use cases of privileged 
access management. 

123
00:07:18,100 --> 00:07:23,300
Now, once you start to get into,
you know, more security driven, 

124
00:07:23,300 --> 00:07:27,800
initiatives, or on the flip 
side, more audit and compliance 

125
00:07:27,800 --> 00:07:32,300
initiatives, that's where things
like monitoring video. 

126
00:07:32,300 --> 00:07:38,300
Monitoring key logging proxy. 
Jump box, jump server type of 

127
00:07:38,300 --> 00:07:41,000
Technologies. 
And then if you are on the audit

128
00:07:41,000 --> 00:07:44,900
and compliance, that's where 
reporting and analytics and 

129
00:07:44,900 --> 00:07:47,600
those types of details really 
are important. 

130
00:07:47,800 --> 00:07:52,500
So just a few of those core use 
cases and core components that 

131
00:07:52,500 --> 00:07:56,000
organizations look to when they 
think about privileged access 

132
00:07:56,000 --> 00:07:58,600
management. 
You know, I often work with 

133
00:07:58,600 --> 00:08:03,100
clients who are at a fairly 
basic level of privileged access

134
00:08:03,100 --> 00:08:06,700
management and one of the 
recommendations that I like to 

135
00:08:06,700 --> 00:08:10,400
make like you can do this right 
away is not having 

136
00:08:10,400 --> 00:08:14,100
administrators have like their 
main user account and do made 

137
00:08:14,100 --> 00:08:18,800
administrator so that if they do
get They do fumble, their 

138
00:08:18,800 --> 00:08:23,100
password and kind of a phishing 
attack or something that that 

139
00:08:23,100 --> 00:08:25,600
person doesn't get their domain 
admin account. 

140
00:08:25,600 --> 00:08:28,700
So then the question becomes now
that I've got two accounts, I've

141
00:08:28,700 --> 00:08:32,400
got my Jim McDonald account, Jim
McDonald admin account. 

142
00:08:32,500 --> 00:08:36,299
My question for you would be, 
does it make sense to use my 

143
00:08:36,400 --> 00:08:40,400
privileged access management 
tool to manage that domain 

144
00:08:40,400 --> 00:08:42,200
admin? 
Jim McDonald account? 

145
00:08:42,400 --> 00:08:45,100
Absolutely. 
Yes. 

146
00:08:45,300 --> 00:08:48,400
And that's where, you know, 
Dated privileges come in. 

147
00:08:48,400 --> 00:08:52,300
They should be just on time. 
They should be need to have on 

148
00:08:52,300 --> 00:08:56,200
specific tasks relevant to an 
individual's role. 

149
00:08:56,600 --> 00:09:01,100
And like you said, you know, 
these accounts are targets for 

150
00:09:01,100 --> 00:09:05,200
hackers and sometimes things 
happen and they do get 

151
00:09:05,200 --> 00:09:08,500
compromised. 
And that's where you need robust

152
00:09:08,500 --> 00:09:12,400
security controls in place that 
can help, you know, stop that 

153
00:09:12,400 --> 00:09:14,400
breed. 
Shut that bridge down prevent 

154
00:09:14,400 --> 00:09:17,100
any type of lateral movements 
from that bridge. 

155
00:09:17,400 --> 00:09:21,400
Isolate any type of monitoring 
that can be done for friends, I 

156
00:09:21,408 --> 00:09:23,200
can Alice's and things like 
that. 

157
00:09:23,300 --> 00:09:27,400
That is really where the benefit
and the criticality of Pam 

158
00:09:27,400 --> 00:09:31,500
tools, come and play. 
Yeah, I mean I feel the same 

159
00:09:31,500 --> 00:09:33,800
way. 
I also think like if you think 

160
00:09:33,800 --> 00:09:37,100
about privileged access 
management for me, the bread and

161
00:09:37,100 --> 00:09:41,100
butter is about human beings, 
not knowing passwords, right? 

162
00:09:41,100 --> 00:09:45,400
So that the system knows, the 
passwords are vaulted, they get 

163
00:09:45,400 --> 00:09:47,100
changed behind the scenes and 
people. 

164
00:09:47,200 --> 00:09:49,900
People don't go home and have 
the password. 

165
00:09:50,000 --> 00:09:52,500
Exactly. 
That's very important. 

166
00:09:52,500 --> 00:09:56,400
And I often describe it, as if a
human knows, the password is 

167
00:09:56,400 --> 00:10:00,000
probably not a safe password or 
a good password. 

168
00:10:00,000 --> 00:10:00,600
Yeah. 
Right. 

169
00:10:00,600 --> 00:10:04,100
I mean, you know what human 
could remember, 32 character, 

170
00:10:04,500 --> 00:10:12,000
random digit password, so, 
that's a good point as well, you

171
00:10:12,000 --> 00:10:13,200
know? 
I'm thinking about some of the 

172
00:10:13,200 --> 00:10:18,300
newer use cases that I'm seeing,
you know, BC have come up over 

173
00:10:18,300 --> 00:10:22,200
the past few years and what the 
role of privileged access 

174
00:10:22,200 --> 00:10:24,400
management would be in. 
So what I'm specifically 

175
00:10:24,400 --> 00:10:28,300
thinking about is like Cloud 
infrastructure and platform as a

176
00:10:28,300 --> 00:10:31,600
service. 
So AWS, Microsoft Azure things 

177
00:10:31,600 --> 00:10:35,100
like that. 
I'm also the about devops and, 

178
00:10:35,200 --> 00:10:38,000
you know, automation through 
Bots, for rolling out 

179
00:10:38,000 --> 00:10:41,300
infrastructure and they often 
have hard-coded passwords and 

180
00:10:41,300 --> 00:10:45,200
then iot use cases. 
So, I'm kind of wondering, are 

181
00:10:45,200 --> 00:10:46,700
you seeing a lot of that as 
well? 

182
00:10:46,700 --> 00:10:49,500
Kind of All into the privileged,
access management facing. 

183
00:10:49,500 --> 00:10:52,900
Is that the right? 
Is privileged access management,

184
00:10:52,900 --> 00:10:56,000
the right place to kind of 
handle, those use cases. 

185
00:10:56,300 --> 00:10:58,600
Absolutely. 
I think more and more 

186
00:10:58,600 --> 00:11:01,900
organizations are looking at 
different areas or different 

187
00:11:01,900 --> 00:11:06,600
aspects of privilege. 
And looking to, you know, 

188
00:11:07,000 --> 00:11:10,300
privileged access management 
organizations or vendors to help

189
00:11:10,300 --> 00:11:14,200
them solve those new challenges 
that are emerging with things 

190
00:11:14,200 --> 00:11:20,500
like iot and devops and the 
explosion of cloud adoption I 

191
00:11:20,500 --> 00:11:24,600
think You that is familiar with 
these AWS and Azure or whatever 

192
00:11:24,600 --> 00:11:28,200
flavor of infrastructure as a 
service, you know, you prefer. 

193
00:11:28,200 --> 00:11:32,100
These environments have very, 
very granular types of 

194
00:11:32,100 --> 00:11:34,200
permissions. 
And you know what? 

195
00:11:34,200 --> 00:11:38,200
I often have experienced talking
to organizations is, it's just 

196
00:11:38,200 --> 00:11:41,000
too much. 
They often don't have a good way

197
00:11:41,000 --> 00:11:43,900
of approaching it. 
It's, you know, that idea of, 

198
00:11:44,000 --> 00:11:48,600
you know, too much complexity. 
I firmly believe in usable 

199
00:11:48,600 --> 00:11:50,900
security and complexity being 
the enemy. 

200
00:11:51,100 --> 00:11:53,200
Of security. 
You guys are familiar with that,

201
00:11:53,200 --> 00:11:58,100
Bruce schneier idea, but again, 
I think, you know, more and more

202
00:11:58,100 --> 00:12:03,100
organizations are changing how 
they Define privilege and it's 

203
00:12:03,100 --> 00:12:06,900
absolutely including some of 
these cloud devops and and 

204
00:12:06,900 --> 00:12:12,200
non-human types of accounts like
Robotics iot and another types 

205
00:12:12,200 --> 00:12:14,700
of accounts that we see. 
And there's so much to learn 

206
00:12:14,900 --> 00:12:16,800
when it comes to privileged 
access management and a lot of 

207
00:12:16,800 --> 00:12:19,900
these newer use cases, you know,
you can spend you know, almost 

208
00:12:19,900 --> 00:12:23,000
all your time. 
Figuring out what's next and how

209
00:12:23,000 --> 00:12:25,600
to tackle some of these new 
challenges, I'm curious because 

210
00:12:25,600 --> 00:12:28,900
what you mentioned earlier that 
you know you didn't really know 

211
00:12:28,900 --> 00:12:31,000
a search media was going into 
this. 

212
00:12:31,300 --> 00:12:36,000
And now here you are, you know, 
you know an expert on Pam and 

213
00:12:36,000 --> 00:12:38,000
privileged access management 
those sorts of things, right? 

214
00:12:38,500 --> 00:12:40,800
And you're responsible for 
Knowledge Management and 

215
00:12:40,800 --> 00:12:44,500
training with psychotic, how do 
you go about? 

216
00:12:44,500 --> 00:12:46,000
Well, first of all, how did you 
get into that? 

217
00:12:46,000 --> 00:12:48,900
Type of rule, is that something 
that you start off with or was 

218
00:12:48,900 --> 00:12:50,900
it something that you kind of 
accumulated? 

219
00:12:51,000 --> 00:12:56,700
A as a as a responsibility as 
you went through that kotik, it 

220
00:12:57,000 --> 00:13:01,000
very similarly to my you know, 
experience in. 

221
00:13:01,000 --> 00:13:06,300
I am I stumbled into the trainer
role for years and years I was 

222
00:13:06,300 --> 00:13:10,200
doing different types of roles 
at psychotic whether it was 

223
00:13:10,200 --> 00:13:14,900
sales or marketing or Channel 
and as we would hire I would 

224
00:13:14,900 --> 00:13:20,600
always help train and teach 
people things because as one of 

225
00:13:20,600 --> 00:13:24,600
the Employees at psychotic. 
I had to kind of teach myself 

226
00:13:24,600 --> 00:13:28,100
these Concepts and understand 
what was going on from a 

227
00:13:28,100 --> 00:13:32,300
technical perspective. 
And so I think I really focused 

228
00:13:32,300 --> 00:13:36,200
on taking these technical 
complex topics and simplifying 

229
00:13:36,200 --> 00:13:40,600
them and it made it a natural 
fit for me to then transition 

230
00:13:40,600 --> 00:13:45,700
into the trainer role. 
And as we grew, it became 

231
00:13:45,700 --> 00:13:49,900
abundantly clear that we needed 
a dedicated person that was 

232
00:13:49,900 --> 00:13:52,700
going to help with. 
With the massive amount of 

233
00:13:52,700 --> 00:13:54,700
growth that psychotic is 
experienced. 

234
00:13:54,900 --> 00:13:58,500
So yeah, I really just kind of 
fell into it, so it would be a 

235
00:13:58,508 --> 00:14:02,500
twenty20 conversation without 
mention of pandemic and covid 

236
00:14:02,500 --> 00:14:07,200
and things like that. 
How has, how has the pandemic 

237
00:14:07,600 --> 00:14:11,900
impacted the way that either you
deliver or think about, you 

238
00:14:11,900 --> 00:14:14,400
know, training for four 
different concepts that are out 

239
00:14:14,400 --> 00:14:19,300
there prior to the pandemic, all
the training I would do on most 

240
00:14:19,300 --> 00:14:20,900
of the training, I would do was 
in person. 

241
00:14:21,500 --> 00:14:26,100
So whether that was, you know, 
in-house, our staff training, 

242
00:14:26,400 --> 00:14:29,100
whether it was new hires or just
start our weekly training, 

243
00:14:29,100 --> 00:14:32,900
Cadence that we pull off. 
It was always in person. 

244
00:14:33,200 --> 00:14:36,800
I also would attend a lot of 
partner events and conferences 

245
00:14:36,800 --> 00:14:39,800
and things like that to help 
educate and evangelize on 

246
00:14:39,800 --> 00:14:44,200
privileged access management and
those days are on pause. 

247
00:14:44,600 --> 00:14:47,900
So there's no more days of 
showing up in person. 

248
00:14:48,300 --> 00:14:51,000
Everything is now done 
digitally. 

249
00:14:51,300 --> 00:14:57,200
So, we are very much focused on 
webinars and podcasts and video 

250
00:14:57,200 --> 00:14:59,600
enabled. 
Many learning enablement. 

251
00:14:59,700 --> 00:15:03,000
And just, you know, different 
forms of Education and Training 

252
00:15:03,200 --> 00:15:06,700
other than the live in person. 
Because, you know, right now, 

253
00:15:06,700 --> 00:15:11,400
that's not safe, but I'm hopeful
that sooner or later, we will be

254
00:15:11,400 --> 00:15:16,200
able to re-establish in-person 
training because I do see value 

255
00:15:16,200 --> 00:15:19,200
in having that face-to-face. 
I think, you know, some things 

256
00:15:19,200 --> 00:15:22,800
are just easier to Understand 
when you're all in a room 

257
00:15:22,800 --> 00:15:27,600
together and as an educator, I 
feel a closer connection with 

258
00:15:27,600 --> 00:15:30,800
the students when I can see the 
look in their eyes. 

259
00:15:30,800 --> 00:15:34,700
And, you know, read their facial
expressions to really understand

260
00:15:34,700 --> 00:15:37,400
our they comprehending. 
What I'm saying or do I need to 

261
00:15:37,400 --> 00:15:40,700
use, you know, different way of 
explaining or, you know, Draw 

262
00:15:40,700 --> 00:15:43,000
Something on the Whiteboard or 
whatever the case may be. 

263
00:15:43,000 --> 00:15:45,400
Yeah, there's no substitute for 
kind of like the hallway 

264
00:15:45,400 --> 00:15:48,800
conversations and, you know, the
site side stuff that kind of 

265
00:15:48,808 --> 00:15:51,000
takes place right in between 
sessions, things like that. 

266
00:15:51,200 --> 00:15:55,200
I feel the same way about that, 
what's been, the hardest thing 

267
00:15:55,200 --> 00:15:59,200
or challenge that you've had to 
overcome kind of adopting or 

268
00:15:59,200 --> 00:16:01,300
adapting? 
I should say into this, new, new

269
00:16:01,300 --> 00:16:05,100
model, with remote delivery, I 
think scalability, I mean, 

270
00:16:05,100 --> 00:16:09,100
everyone's online. 
Now, I'm sure everyone has 

271
00:16:09,600 --> 00:16:13,100
experienced some sort of 
resource constraints. 

272
00:16:13,500 --> 00:16:17,900
And so really just setting up 
our program transferring, 

273
00:16:17,900 --> 00:16:20,500
everything we would do in person
face-to-face. 

274
00:16:21,200 --> 00:16:25,900
Digital environment and then 
empowering that program to scale

275
00:16:26,200 --> 00:16:28,800
that has also been a challenge. 
You know, that kind of gives a 

276
00:16:28,808 --> 00:16:32,100
global organization 
cybersecurity threats are 

277
00:16:32,100 --> 00:16:34,600
Global. 
So we're always thinking about, 

278
00:16:34,600 --> 00:16:37,000
you know, our customers, and 
partners in the media or in a 

279
00:16:37,000 --> 00:16:41,000
pack, or last time wherever it 
is that, you know, we're helping

280
00:16:41,000 --> 00:16:42,900
folks so. 
So I'm sure you have some pretty

281
00:16:42,900 --> 00:16:45,800
good stories, around different 
training sessions, may be, that 

282
00:16:45,800 --> 00:16:49,200
you've conducted orbit at least 
been a part of any time, feel 

283
00:16:49,200 --> 00:16:52,600
free to protect the names of the
LT and or Innocent. 

284
00:16:52,800 --> 00:16:55,900
But do you have, you know, what 
was kind of like the best 

285
00:16:56,000 --> 00:16:58,300
training Story You've Got and 
maybe what's one? 

286
00:16:58,300 --> 00:17:00,600
That would be. 
Let's call it less than ideal. 

287
00:17:00,700 --> 00:17:04,599
So this is actually pretty crazy
story if you're ready for this 

288
00:17:04,599 --> 00:17:09,900
one. 
So I was privileged enough to 

289
00:17:09,900 --> 00:17:15,599
deliver a training session at 
the US Embassy in London. 

290
00:17:16,099 --> 00:17:18,099
And I was working with a 
partner. 

291
00:17:18,099 --> 00:17:22,400
We were presenting in the 
basement of the US Embassy and 

292
00:17:22,400 --> 00:17:28,099
we were talking Insider threat 
and I was literally in the 

293
00:17:28,099 --> 00:17:31,000
middle of my presentation 
standing out talking showing 

294
00:17:31,000 --> 00:17:37,000
slides, engaging with it, the 
group and the power went out 

295
00:17:37,000 --> 00:17:42,100
only we were in the basement, so
there's no windows and at first,

296
00:17:42,100 --> 00:17:45,200
I wasn't quite sure if it was 
the power that went out. 

297
00:17:46,700 --> 00:17:49,200
You know, God forbid if it was 
like terrorist attack or I 

298
00:17:49,208 --> 00:17:52,500
didn't, I didn't know what had 
happened at the US Embassy, but 

299
00:17:52,500 --> 00:17:55,600
I knew that all of a sudden I 
was presenting and then split 

300
00:17:55,600 --> 00:17:57,800
seconds later. 
I was in the dark and we were 

301
00:17:57,800 --> 00:18:01,000
all in the dark and everyone 
just kind of froze. 

302
00:18:01,300 --> 00:18:04,800
And no one said a thing for a 
few seconds and it was probably 

303
00:18:04,800 --> 00:18:06,500
only three or four or five 
seconds. 

304
00:18:06,500 --> 00:18:10,800
It was very, very short if and 
then the power kick back on and 

305
00:18:10,800 --> 00:18:14,500
we all just kind of acknowledge 
that we were still there and we 

306
00:18:14,500 --> 00:18:16,900
didn't really know what happened
and we We weren't going to ask 

307
00:18:16,900 --> 00:18:20,200
what happened, but we kind of 
put aside the training and just 

308
00:18:20,200 --> 00:18:23,400
kind of talked and moved onto 
the coffee phase. 

309
00:18:23,400 --> 00:18:28,100
And yeah it was it was a really 
interesting session so you went 

310
00:18:28,100 --> 00:18:30,900
from from from Village access 
management to an episode of 

311
00:18:30,900 --> 00:18:34,600
Homeland and exactly what 
exactly 

312
00:18:46,600 --> 00:18:49,800
We got to figure out Jim, how we
can get to, you know, some some 

313
00:18:49,800 --> 00:18:52,400
International location and and 
do something on those lines 

314
00:18:52,400 --> 00:18:56,200
because I feel got a little of a
James Bond, kind of themed that.

315
00:18:56,200 --> 00:18:59,000
It's so DC. 
I feel like, I've been very 

316
00:18:59,000 --> 00:19:02,000
blessed. 
I have luckily been invited to 

317
00:19:02,000 --> 00:19:05,900
lots of embassies here in DC. 
And, of course, when I travel 

318
00:19:05,900 --> 00:19:07,800
abroad, I usually get the 
invited as well. 

319
00:19:07,800 --> 00:19:11,600
It's a, it's a, it's a DC thing,
I'm telling, you are the 

320
00:19:11,600 --> 00:19:16,600
Beltway, right? 
So if if I am, you know, Part of

321
00:19:16,600 --> 00:19:18,300
an Enterprise. 
I am program somewhere, and I'm 

322
00:19:18,300 --> 00:19:22,600
running either Pam, or maybe 
just even, I am General as part 

323
00:19:22,600 --> 00:19:27,200
of a program at my organization.
What are some tips that I could 

324
00:19:27,200 --> 00:19:32,100
use to develop my own, either 
in-house training or some ideas.

325
00:19:32,100 --> 00:19:34,600
You might have to help kind of 
bring along parts of my 

326
00:19:34,600 --> 00:19:40,100
organization that maybe aren't 
as you know, tech savvy when it 

327
00:19:40,100 --> 00:19:42,200
comes to I am or even Pam 
specifically. 

328
00:19:42,200 --> 00:19:47,600
So I think, you know, security 
training and Weekly identity and

329
00:19:47,600 --> 00:19:52,900
access management training for 
all levels and all shades of 

330
00:19:52,900 --> 00:19:57,600
grey when it comes to technical 
capabilities is so important. 

331
00:19:57,600 --> 00:20:01,300
And in my opinion, is a 
milestone of maturity within the

332
00:20:01,300 --> 00:20:06,900
program because all people need 
to be educated on why why you 

333
00:20:06,900 --> 00:20:08,800
don't click the link. 
Why you don't open the 

334
00:20:08,800 --> 00:20:11,400
attachment, right? 
Why you need a long and complex 

335
00:20:11,400 --> 00:20:13,500
password? 
Why we're asking you to change 

336
00:20:13,500 --> 00:20:16,100
your password every 90 days or 
45 days. 

337
00:20:16,300 --> 00:20:18,200
Days or whatever. 
The case might be based on the 

338
00:20:18,200 --> 00:20:21,900
organization and then again, as 
you scale up to the more 

339
00:20:21,900 --> 00:20:24,400
complex, technical use cases and
audiences. 

340
00:20:24,600 --> 00:20:26,400
Again, they need to be part of 
the process. 

341
00:20:26,600 --> 00:20:31,300
They need to have buy-in and in 
my experience, especially, you 

342
00:20:31,300 --> 00:20:34,200
know, with some of the tools and
capabilities that we work with. 

343
00:20:34,500 --> 00:20:42,000
It's not a barrier because we're
providing a lot of Automation 

344
00:20:42,000 --> 00:20:46,100
and hopefully we're taking a lot
of manual processes off. 

345
00:20:46,300 --> 00:20:49,300
Plate once they kind of 
understand from a security 

346
00:20:49,300 --> 00:20:52,200
perspective of why that's so 
important. 

347
00:20:52,200 --> 00:20:55,500
And why you know, the 
organization is asking them to 

348
00:20:55,500 --> 00:21:02,600
do X Y or Z people buy into it 
and you know, I did a training 

349
00:21:02,600 --> 00:21:06,300
for what I call the math team 
which is really our controller 

350
00:21:06,300 --> 00:21:09,100
and our accountant and our 
billing people I call them the 

351
00:21:09,100 --> 00:21:12,000
math team. 
So I was doing a training for 

352
00:21:12,000 --> 00:21:13,500
them. 
This might have been here to 

353
00:21:13,500 --> 00:21:16,100
ago, but I started talking about
you. 

354
00:21:16,300 --> 00:21:19,800
No, the nature of breaches and 
how these threats, you know, 

355
00:21:19,800 --> 00:21:23,900
play out and some of the tools 
and how hackers hack and people 

356
00:21:23,900 --> 00:21:27,300
are so interested in that they 
asked me to come back, they 

357
00:21:27,300 --> 00:21:30,500
asked if they could have another
training session just to talk 

358
00:21:30,500 --> 00:21:33,700
more and to learn more about, 
you know what the iconic does 

359
00:21:33,700 --> 00:21:36,800
and what I do and you know, 
what's going on in the industry.

360
00:21:36,800 --> 00:21:39,500
And so I think people are 
genuinely interested and they're

361
00:21:39,500 --> 00:21:43,100
curious and so, you know, 
simplifying training, that's 

362
00:21:43,100 --> 00:21:47,200
very important, but having that 
all inclusive approach, For all 

363
00:21:47,200 --> 00:21:50,900
your different areas of the 
business and your different 

364
00:21:50,900 --> 00:21:53,700
shades of grey when it comes to 
technical audiences and your 

365
00:21:53,700 --> 00:21:58,400
different areas and aspects of 
privilege and identity are very 

366
00:21:58,400 --> 00:21:59,800
important. 
Does that make sense? 

367
00:21:59,800 --> 00:22:03,900
Guys make science to makes a lot
of sense, your KD, I think 

368
00:22:03,900 --> 00:22:07,600
there's probably a lot of our 
listeners out there like hearing

369
00:22:07,600 --> 00:22:13,000
you and thinking man, what a 
cool job Katie has and I'd like 

370
00:22:13,000 --> 00:22:15,800
to do something like that. 
So I'm wondering, you know, 

371
00:22:15,800 --> 00:22:21,200
obviously Lee, there's many 
paths to get to the end but do 

372
00:22:21,200 --> 00:22:24,000
you have any advice for for 
someone who might be interested 

373
00:22:24,000 --> 00:22:27,000
in doing what you do? 
Don't be shy. 

374
00:22:27,200 --> 00:22:29,900
Be proactive. 
I think that's, you know, one of

375
00:22:29,900 --> 00:22:35,400
the most important parts is you 
have to, you know, take action 

376
00:22:35,400 --> 00:22:38,700
to get into this industry. 
I've seen lots and lots of 

377
00:22:38,700 --> 00:22:43,900
people start like me where they 
get in the door in a completely 

378
00:22:43,900 --> 00:22:46,200
different role. 
So maybe they come. 

379
00:22:46,400 --> 00:22:50,100
Is a tech support person or 
maybe they come in as a sales 

380
00:22:50,100 --> 00:22:53,700
person, or a marketing person, 
or a developer, you know, 

381
00:22:53,700 --> 00:22:56,400
whatever the case may be and 
then just through natural 

382
00:22:56,400 --> 00:23:01,000
education and evolution their 
position changes. 

383
00:23:01,000 --> 00:23:03,500
And you know, they have the 
ability to do something 

384
00:23:03,500 --> 00:23:05,800
different and focus on cyber 
security. 

385
00:23:06,900 --> 00:23:10,700
So I would say, you know, show 
up Reach Out connect on 

386
00:23:10,700 --> 00:23:12,600
LinkedIn. 
If there's a local group that 

387
00:23:12,600 --> 00:23:15,800
you want to, you know aisaka or 
some of the other industry 

388
00:23:15,800 --> 00:23:19,300
groups I think are so important.
I'm sure lots of over holding 

389
00:23:19,300 --> 00:23:24,400
digital events when Global 
pandemic whole thing going on. 

390
00:23:24,700 --> 00:23:27,900
But I think there's lots of ways
to just kind of force yourself 

391
00:23:27,900 --> 00:23:31,200
into the community and be 
proactive about it. 

392
00:23:31,200 --> 00:23:34,600
Yeah, I feel so fortunate that 
I've ended up in this industry. 

393
00:23:34,600 --> 00:23:39,400
I think it's such a cool 
industry and I know when I've 

394
00:23:39,400 --> 00:23:41,800
been attending, I am 
conferences. 

395
00:23:41,800 --> 00:23:45,300
When we still had in-person 
conferences, you know, 15 years 

396
00:23:45,300 --> 00:23:48,600
ago. 
Look left and look right and 

397
00:23:48,600 --> 00:23:51,900
more than likely people on both 
sides, you were were men. 

398
00:23:52,200 --> 00:23:55,300
And now I'm seeing many more 
women enter this industry which 

399
00:23:55,300 --> 00:24:00,600
I think is a very positive 
development but wondering you 

400
00:24:00,600 --> 00:24:07,600
know what advice you might have.
For women who are in, I am or 

401
00:24:07,600 --> 00:24:13,200
are looking to get into. 
I am to kind of make that move. 

402
00:24:13,300 --> 00:24:15,200
Well, what kind of advice might 
you have for them? 

403
00:24:15,300 --> 00:24:19,800
Confidence is Is key, do not let
the men in the room intimidate. 

404
00:24:19,800 --> 00:24:25,900
You it is very often that I am. 
The only woman in the room and 

405
00:24:25,900 --> 00:24:29,000
some women are not comfortable 
with that. 

406
00:24:29,000 --> 00:24:34,600
And I think it's a mean there's 
the old adage, right? 

407
00:24:34,600 --> 00:24:37,400
That the magic happens when you 
step outside your comfort zone. 

408
00:24:37,400 --> 00:24:42,900
But I truly believe that in some
ways I think on some level you 

409
00:24:42,900 --> 00:24:46,200
just have to fake it until you 
really are comfortable with it. 

410
00:24:47,700 --> 00:24:51,900
And it's also important to be on
top of your game. 

411
00:24:51,900 --> 00:24:55,700
So I think, you know, part of 
the reason why I have such a 

412
00:24:55,700 --> 00:25:00,100
depth and breadth of knowledge 
is because I've forced myself to

413
00:25:00,300 --> 00:25:04,700
develop this, I always want to 
be able to answer a question and

414
00:25:04,700 --> 00:25:06,500
it's okay to not have an answer,
right. 

415
00:25:06,500 --> 00:25:10,700
But I pride myself on having a 
very few questions that I cannot

416
00:25:10,700 --> 00:25:16,100
answer. 
Yeah, and I can vouch for you. 

417
00:25:16,300 --> 00:25:19,700
Kind of speaking with confidence
and I think that's important. 

418
00:25:20,900 --> 00:25:23,500
Whoever you are like to go in 
there when you speak with 

419
00:25:23,500 --> 00:25:26,500
confidence. 
I think that people are more 

420
00:25:26,500 --> 00:25:31,400
likely to agree with what you 
say and I always say it's like 

421
00:25:31,500 --> 00:25:33,800
it's like sharks can smell blood
in the water. 

422
00:25:34,500 --> 00:25:36,000
You don't sound confident? 
What? 

423
00:25:36,000 --> 00:25:38,500
You have to say whether it's 
true or not. 

424
00:25:38,700 --> 00:25:42,200
People are going to think that 
maybe it's not true. 

425
00:25:43,100 --> 00:25:45,100
I'm also wondering, you know. 
Okay. 

426
00:25:45,100 --> 00:25:49,400
Did you have Mentors in your 
career either, you know, formal 

427
00:25:49,400 --> 00:25:52,900
mentors or just people in 
formerly mentored you. 

428
00:25:52,900 --> 00:25:56,800
And I'm wondering how that that 
helped you in terms of building 

429
00:25:56,800 --> 00:26:00,800
your career, this is a little 
cheesy and very personal but my 

430
00:26:00,800 --> 00:26:05,700
mom has always been my mentor. 
So, for years and years and 

431
00:26:05,700 --> 00:26:10,400
years, she was a very Savvy 
businesswoman, she was a 

432
00:26:10,400 --> 00:26:13,400
trendsetter within her own 
industry. 

433
00:26:14,300 --> 00:26:17,900
So she was one of the first 
women Eamon hired into the 

434
00:26:17,900 --> 00:26:24,100
financial management program at 
GE, she was one of two and she 

435
00:26:24,100 --> 00:26:31,400
was just a very driven Savvy 
educated business woman and I 

436
00:26:31,400 --> 00:26:36,400
think I've always strived to 
have her same sort of business 

437
00:26:36,400 --> 00:26:40,300
success. 
And again, I just kind of got 

438
00:26:40,300 --> 00:26:45,300
lucky and stumbled into Tech and
cyber security and identity and 

439
00:26:45,300 --> 00:26:48,900
access management. 
Didn't I don't think I'll ever 

440
00:26:48,900 --> 00:26:51,800
do anything else. 
I think I have found my passion 

441
00:26:51,800 --> 00:26:55,500
and my career choice. 
This is it this is it this is 

442
00:26:55,500 --> 00:26:58,100
where we're going, you know, the
confidence thing I think is 

443
00:26:58,100 --> 00:27:02,700
interesting for me, confidence 
comes from knowing subject 

444
00:27:02,700 --> 00:27:06,800
matter and you know then come 
from other things like being 

445
00:27:06,800 --> 00:27:10,900
able to articulate etcetera. 
Would you would you agree with 

446
00:27:10,900 --> 00:27:12,700
that approach? 
Or do you think that there's a 

447
00:27:12,708 --> 00:27:14,600
different way that people can 
approach kind of building that 

448
00:27:14,600 --> 00:27:16,100
confidence if they don't 
necessarily have it? 

449
00:27:16,200 --> 00:27:21,100
I think it's absolutely about, 
you know, building that and 

450
00:27:21,100 --> 00:27:23,600
developing that through 
education and just knowing your 

451
00:27:23,600 --> 00:27:25,600
stuff. 
But I also think especially for 

452
00:27:25,600 --> 00:27:29,300
women their newer to this 
industry, there's some sort of 

453
00:27:29,300 --> 00:27:32,300
fake it until you got it. 
That has to happen. 

454
00:27:32,600 --> 00:27:36,800
It's in most circumstances. 
Anyways, just because of the 

455
00:27:37,100 --> 00:27:41,300
male-dominated industry that is 
Tech. 

456
00:27:41,300 --> 00:27:44,900
And is really you know, cyber 
security and identity and access

457
00:27:44,900 --> 00:27:46,800
well in still inside. 
Secret. 

458
00:27:46,800 --> 00:27:49,500
I think everybody gets to some 
degree is Faking it until it 

459
00:27:49,500 --> 00:27:52,400
gets up. 
So I think that's good stuff. 

460
00:27:52,900 --> 00:27:56,900
I know we're kind of getting 
here towards the end of the 

461
00:27:56,900 --> 00:27:59,700
topic but what I wanted to talk 
through here with you is some 

462
00:27:59,700 --> 00:28:03,100
predictions, maybe that you 
might have in the privileged 

463
00:28:03,100 --> 00:28:07,800
access management space for 21. 
Is there anything that that you 

464
00:28:07,800 --> 00:28:11,600
think is going to be kind of 
something that you want to throw

465
00:28:11,600 --> 00:28:15,700
out there, as hey, this is 
coming in 2021 and folks should 

466
00:28:15,700 --> 00:28:19,100
be aware About it or at least be
thinking about, you know, how to

467
00:28:19,100 --> 00:28:20,800
approach it. 
I think, you know, some of the 

468
00:28:20,800 --> 00:28:25,300
things we've touched on during 
this call and my I think 

469
00:28:25,300 --> 00:28:30,400
prediction for 2021 is that the 
definition of privileged access 

470
00:28:30,400 --> 00:28:34,300
management is going to change. 
It's no longer going to be that 

471
00:28:34,600 --> 00:28:37,700
traditional infrastructure since
of Pam. 

472
00:28:37,900 --> 00:28:42,800
I think it's going to be cloud 
and devops and iot and you know,

473
00:28:42,800 --> 00:28:47,900
all these other types of 
Privilege in areas of privilege.

474
00:28:47,900 --> 00:28:53,000
And I think that that is really 
going to be, you know, under a 

475
00:28:53,000 --> 00:28:57,200
magnifying glass as the 
pandemic, right? 

476
00:28:57,200 --> 00:29:00,900
Because the digital 
transformation is forced, you 

477
00:29:00,900 --> 00:29:03,100
know, people are no longer in 
the office. 

478
00:29:03,300 --> 00:29:06,600
I don't think people will ever 
go back to the office, the way 

479
00:29:06,600 --> 00:29:09,600
they were. 
And so I think that traditional 

480
00:29:09,600 --> 00:29:13,500
Pam infrastructure security is 
going to be less and less, you 

481
00:29:13,500 --> 00:29:16,400
know, of a priority and more and
more people are going to To be 

482
00:29:16,400 --> 00:29:19,100
thinking about these different 
aspects and arrogance, a 

483
00:29:19,100 --> 00:29:21,000
privilege. 
And it's interesting. 

484
00:29:21,600 --> 00:29:22,800
So I have a couple items on 
that. 

485
00:29:22,800 --> 00:29:27,100
Cutthroat, you rapid-fire format
here for 21, and I'm glad you 

486
00:29:27,100 --> 00:29:28,500
brought up the definition 
change. 

487
00:29:28,500 --> 00:29:31,000
I'm going to put you on the spot
here because this ties right in 

488
00:29:31,000 --> 00:29:34,200
nicely. 
And there's my question will 

489
00:29:34,200 --> 00:29:38,700
Social logins be more widely 
considered privileged accounts? 

490
00:29:38,900 --> 00:29:40,900
Yes. 
Anything that shared should be a

491
00:29:40,908 --> 00:29:44,000
privileged account and has 
visibility for the corporate 

492
00:29:44,000 --> 00:29:46,000
social media. 
Absolutely, that's something 

493
00:29:46,000 --> 00:29:48,100
that I don't see considered very
often right now. 

494
00:29:48,108 --> 00:29:50,900
I think the traditional approach
is, yeah, of course, server 

495
00:29:50,900 --> 00:29:52,900
accounts and shared accounts on 
things like that. 

496
00:29:53,200 --> 00:29:56,500
But when I asked how social 
logins are being managed, it's 

497
00:29:56,500 --> 00:29:58,600
usually kind of like, uh, and it
really kind of thought about 

498
00:29:58,600 --> 00:30:00,800
that. 
I kind of feel like closely 

499
00:30:00,800 --> 00:30:06,800
related to that are accounts 
that maybe are managed by a 

500
00:30:06,800 --> 00:30:10,600
group like accounting to log 
into their Bank of America 

501
00:30:10,600 --> 00:30:12,800
portal or something. 
I'm using that as an example. 

502
00:30:13,000 --> 00:30:17,500
But you know, maybe five people 
In the accounting department, 

503
00:30:17,500 --> 00:30:20,300
login to a third-party web 
application. 

504
00:30:20,300 --> 00:30:21,900
They kind of share that 
password. 

505
00:30:22,300 --> 00:30:26,000
That's one of the probably the 
most dangerous passwords in the 

506
00:30:26,000 --> 00:30:29,800
organization. 
HR systems, accounting systems 

507
00:30:29,800 --> 00:30:32,700
Financial systems, even LMS 
systems. 

508
00:30:32,700 --> 00:30:35,900
Like what I manage there's an 
abundance of intellectual 

509
00:30:35,900 --> 00:30:40,300
property in our LMS. 
There's so many areas of risk. 

510
00:30:40,400 --> 00:30:45,100
It's just that in most senses of
privileged access management, 

511
00:30:45,200 --> 00:30:48,800
you know, It's and folks like 
us, we're only talking to the 

512
00:30:48,800 --> 00:30:50,600
Ops and the infrastructure in 
the security. 

513
00:30:50,600 --> 00:30:54,000
Folks were not talking to the 
other areas of the business and 

514
00:30:54,000 --> 00:30:57,600
helping them Define and 
understand what risks exist 

515
00:30:57,600 --> 00:30:59,400
there. 
And what areas are privileged 

516
00:30:59,400 --> 00:31:02,800
they actually have. 
Because I think there's a lot 

517
00:31:02,800 --> 00:31:04,900
there and we're going to see it 
more and more. 

518
00:31:05,000 --> 00:31:07,300
Yeah, you're right. 
It comes down to risk, right? 

519
00:31:07,400 --> 00:31:11,300
I mean, the risk is there, it 
might not be the most 

520
00:31:11,300 --> 00:31:14,400
straightforward account to 
manage, but that doesn't mean 

521
00:31:14,400 --> 00:31:16,900
that you shouldn't be doing. 
Think about it. 

522
00:31:17,000 --> 00:31:20,100
How about vaults? 
I feel like those are fairly 

523
00:31:20,100 --> 00:31:22,200
traditional at this point, 
almost kind of a commodity 

524
00:31:22,200 --> 00:31:26,100
amongst, you know, the the 
vendors in this space. 

525
00:31:26,100 --> 00:31:30,300
Are we going to see more 
advanced functions being adopted

526
00:31:30,300 --> 00:31:34,600
things like session recording 
application, password 

527
00:31:34,600 --> 00:31:38,200
management, devops Integrations,
you know, for whatever it may be

528
00:31:38,200 --> 00:31:41,700
things like that. 
Do you see more adoption of 

529
00:31:41,708 --> 00:31:45,300
that, or do you think that there
are still a lot of companies 

530
00:31:45,300 --> 00:31:47,800
that maybe don't have? 
Have the basics of privileged 

531
00:31:47,800 --> 00:31:50,100
access management place and that
will still see kind of vaulting 

532
00:31:50,100 --> 00:31:54,000
as the first or most predominant
step in 2021, you know, I think 

533
00:31:54,000 --> 00:31:56,600
there's a good mix of both. 
I do think there's a lot of 

534
00:31:56,600 --> 00:32:00,100
organizations out there that are
still using sticky notes and 

535
00:32:00,100 --> 00:32:04,900
Excel spreadsheets and do need a
vault, I think and I could 

536
00:32:04,900 --> 00:32:07,400
literally probably talk about 
this for like 10 minutes. 

537
00:32:07,400 --> 00:32:11,000
So I will try not to go off on a
tangent but everyone needs. 

538
00:32:11,000 --> 00:32:13,600
A vault, my hundred year old 
grandpa needs involved. 

539
00:32:13,600 --> 00:32:16,000
Children need a vault. 
Everyone has a past. 

540
00:32:16,200 --> 00:32:19,900
Last word problem, everyone has 
a digital identity nowadays. 

541
00:32:20,200 --> 00:32:23,100
I mean, if you think about 
literally children that are 

542
00:32:23,100 --> 00:32:27,900
logging in to their school using
Chromebooks and they have 

543
00:32:27,900 --> 00:32:32,700
different passwords for their 
different school systems and and

544
00:32:32,700 --> 00:32:35,500
everything is digital. 
Now all of those need to be 

545
00:32:35,500 --> 00:32:39,100
password protected and all of 
those should be unique, strong 

546
00:32:39,100 --> 00:32:41,500
passwords that should be in the 
vault. 

547
00:32:41,700 --> 00:32:46,500
So I think there's lots and lots
of use for Vaulting. 

548
00:32:46,500 --> 00:32:50,100
But I also think that more and 
more organizations have kind of 

549
00:32:50,100 --> 00:32:52,800
check that checkbox. 
And now they're starting to 

550
00:32:52,800 --> 00:32:56,200
realize that there are other 
areas of privilege. 

551
00:32:56,200 --> 00:32:59,500
They need to address because of 
that risk that we just 

552
00:32:59,500 --> 00:33:01,900
mentioned. 
Where do you see artificial? 

553
00:33:01,900 --> 00:33:06,400
Intelligence intersecting with 
some of the use cases that are 

554
00:33:06,400 --> 00:33:09,700
traditionally privileged access 
management, like vaulting or 

555
00:33:09,700 --> 00:33:13,000
session recording or you know 
analytics those sorts of things.

556
00:33:13,000 --> 00:33:15,900
Do you see AI or machine 
learning? 

557
00:33:16,600 --> 00:33:20,300
Taking a step forward in the Pam
space. 

558
00:33:20,300 --> 00:33:23,600
I think they have to, I think 
those types of Technologies are 

559
00:33:23,600 --> 00:33:27,900
going to be critical for the 
vendors, in our space to 

560
00:33:27,900 --> 00:33:32,000
embrace, because the 
adversaries, and the hackers are

561
00:33:32,000 --> 00:33:35,600
absolutely going to embrace 
these Technologies. 

562
00:33:35,600 --> 00:33:38,600
And especially when it comes to 
like, AI stuff. 

563
00:33:38,700 --> 00:33:42,800
It's very, very scary to me for 
a threat. 

564
00:33:42,800 --> 00:33:46,000
That doesn't get you the first 
time to learn, why it didn't get

565
00:33:46,100 --> 00:33:48,000
Get you and to get you the 
second time. 

566
00:33:48,200 --> 00:33:52,200
And so for things like that, 
also as Security Professionals 

567
00:33:52,200 --> 00:33:55,800
and as vendors in this space 
need to be aware of that need to

568
00:33:55,800 --> 00:33:59,200
be thinking about that. 
And using those exact same tools

569
00:33:59,200 --> 00:34:04,000
and tricks to defend after list 
is something that has, you know,

570
00:34:04,000 --> 00:34:06,000
been the topic du jour. 
It seems like for the last 

571
00:34:06,000 --> 00:34:09,600
couple of years, and there seems
to be another Focus around 

572
00:34:09,600 --> 00:34:12,699
trying to become password list 
at least in an Enterprise 

573
00:34:12,699 --> 00:34:16,000
situation. 
How do you think this affects 

574
00:34:16,100 --> 00:34:18,800
Access management. 
I called, can I say this? 

575
00:34:19,199 --> 00:34:25,300
I call bullshit. 
I call, I call malarkey. 

576
00:34:25,300 --> 00:34:31,500
I do not think that we are ever 
truly going to get to a password

577
00:34:31,500 --> 00:34:37,800
list State. 
And a great example is the other

578
00:34:37,800 --> 00:34:42,600
day, I was logging into my 
Verizon app on my phone because 

579
00:34:42,600 --> 00:34:46,800
I wanted to pay my Verizon bill 
and the action method that I 

580
00:34:46,800 --> 00:34:49,800
have set up is facial 
recognition on the app and it 

581
00:34:49,800 --> 00:34:53,199
wasn't working. 
So I needed the password, I had 

582
00:34:53,199 --> 00:34:57,800
to pay my bill and so I had to 
log into my Vault and get my 

583
00:34:57,800 --> 00:35:01,100
password and authenticate the 
old school way and there's 

584
00:35:01,100 --> 00:35:06,200
always going to be that need 
when you know MFA or SSO or 

585
00:35:06,200 --> 00:35:08,800
whatever, type of authentication
people are using you know, 

586
00:35:08,808 --> 00:35:13,200
doesn't work or even you know 
basic other tasks like restoring

587
00:35:13,200 --> 00:35:15,000
from backups, right? 
You're going to need the 

588
00:35:15,000 --> 00:35:18,800
password. 
I think there's, you know, 

589
00:35:18,800 --> 00:35:24,700
circumstances for not using 
passwords but I also think that 

590
00:35:24,700 --> 00:35:27,800
it's never going to completely 
just my two cents. 

591
00:35:27,900 --> 00:35:30,400
What's the next Frontier for 
privileged access management? 

592
00:35:30,400 --> 00:35:36,100
I think it's what we've kind of 
touched on which is this area of

593
00:35:36,100 --> 00:35:41,900
privilege, that is expanding and
evolving these Cloud assets. 

594
00:35:41,900 --> 00:35:45,900
These different areas of 
privilege, iot non-human and 

595
00:35:46,000 --> 00:35:54,000
Counts robotics I think you know
it's very scary when people ring

596
00:35:54,000 --> 00:35:58,800
doorbell, cameras, get hacked 
every seems like almost every 

597
00:35:58,800 --> 00:36:01,100
single day. 
I watched, you know, the evening

598
00:36:01,100 --> 00:36:05,700
national news and they have some
story about this device or that 

599
00:36:05,700 --> 00:36:09,300
device or you know what you need
to do to better secure yourself 

600
00:36:09,300 --> 00:36:13,600
from this cyber security threat.
So I think, you know, all of 

601
00:36:13,600 --> 00:36:17,700
these areas of privilege are 
going Continue to be more and 

602
00:36:17,700 --> 00:36:21,500
more relevant, not only in a 
business environment, but also, 

603
00:36:21,500 --> 00:36:26,300
you know, in a consumer and you 
know, end-user at whatever you 

604
00:36:26,300 --> 00:36:29,100
want to call it non-technical 
way as well. 

605
00:36:29,200 --> 00:36:30,600
Yeah, I think I think it was 
back, right? 

606
00:36:30,600 --> 00:36:35,500
That definition evolving and you
know this as definitions evolved

607
00:36:35,500 --> 00:36:38,300
for privileged access. 
The scope will most likely have 

608
00:36:38,300 --> 00:36:40,200
Hall with that, right? 
What's included as part of that 

609
00:36:40,200 --> 00:36:43,000
and then making sure that you're
taking the right steps to secure

610
00:36:43,000 --> 00:36:47,100
those keys to the castle. 
So, Well, I certainly appreciate

611
00:36:47,100 --> 00:36:49,600
the conversation and I know that
we're kind of coming up here on 

612
00:36:49,600 --> 00:36:54,600
time before we close things out 
for the year. 

613
00:36:55,600 --> 00:36:58,700
Are there any, you know, final 
words of wisdom that you want to

614
00:36:58,700 --> 00:37:05,100
share with the group Katie, um, 
get your shot, don't be scared, 

615
00:37:05,500 --> 00:37:07,900
don't be scared to do your part 
to help us shut down the 

616
00:37:07,900 --> 00:37:09,300
pandemic. 
Exactly. 

617
00:37:10,700 --> 00:37:15,200
But more importantly, you know, 
change your password, if you can

618
00:37:15,200 --> 00:37:20,200
do one thing, In 2021 that will 
help keep your digital identity 

619
00:37:20,200 --> 00:37:23,300
secure. 
It is definitely make sure you 

620
00:37:23,300 --> 00:37:26,600
change your password at the 
start of the new year. 

621
00:37:26,800 --> 00:37:29,400
That's always a good best 
practice and then put that in a 

622
00:37:29,400 --> 00:37:32,400
vault and make sure that you're 
using a different password for 

623
00:37:32,400 --> 00:37:34,900
as many sites as you can no 
daisy chain. 

624
00:37:49,200 --> 00:37:51,800
Having different passwords and 
having strong passwords and not 

625
00:37:51,800 --> 00:37:54,800
even have to remember that is a 
big Advantage for folks. 

626
00:37:54,800 --> 00:37:57,700
So definitely agree with that. 
Jim is there anything that you'd

627
00:37:57,700 --> 00:38:00,700
like to toss out there? 
Before we let these fine folks 

628
00:38:00,700 --> 00:38:04,300
go for the year? 
Well, a few things, so personal 

629
00:38:04,300 --> 00:38:06,600
that was the most practical 
advice. 

630
00:38:06,800 --> 00:38:11,400
I think any, including you, and 
I have give any one of our 

631
00:38:11,400 --> 00:38:14,700
guests. 
I've given what cages said about

632
00:38:14,700 --> 00:38:18,800
the password, Changing. 
I mean New Year, like, that's a 

633
00:38:19,200 --> 00:38:23,700
great practice to get into, but 
the other thing I was thinking, 

634
00:38:23,700 --> 00:38:28,900
is I very much feel like I would
have been great as a writer on 

635
00:38:28,900 --> 00:38:33,400
Seinfeld because my observations
are about, you know, nothing 

636
00:38:33,400 --> 00:38:35,800
partner there about like the 
smaller things. 

637
00:38:35,800 --> 00:38:39,400
So Jack, you always say keys to 
the castle. 

638
00:38:39,700 --> 00:38:44,100
I always say keys to the kingdom
and I'm wondering Katie, which 

639
00:38:44,100 --> 00:38:45,800
of us is, right? 
Is a key step. 

640
00:38:46,000 --> 00:38:49,600
Cast of piece of the Kingdom, 
but isn't the castle? 

641
00:38:49,600 --> 00:38:51,200
The kingdom. 
I don't know. 

642
00:38:52,200 --> 00:38:57,200
I'm starting to worry keys to 
the city or something keys to 

643
00:38:57,200 --> 00:38:59,100
the Galaxy. 
I just want to throw out there. 

644
00:38:59,100 --> 00:39:02,600
Just remember, who is editing 
this podcast? 

645
00:39:02,600 --> 00:39:03,600
I'm just gonna throw that out 
there. 

646
00:39:03,600 --> 00:39:10,800
Okay, what's your answer? 
Katie keys to the castle that 

647
00:39:10,800 --> 00:39:14,100
was, that was not peer pressure 
or any type of blackmail or 

648
00:39:14,100 --> 00:39:18,300
extortion at all for editing. 
Versus Jeff is right, okay? 

649
00:39:18,400 --> 00:39:22,300
So, the last thing I just wanted
to say is I hope everybody and 

650
00:39:22,300 --> 00:39:24,600
gets to have a little bit of a 
break here at the end of the 

651
00:39:24,600 --> 00:39:26,300
year. 
Comes back with their batteries 

652
00:39:26,300 --> 00:39:31,300
recharged for. 
For me personally, 2020 was 

653
00:39:32,900 --> 00:39:37,900
busier than most years while we 
weren't doing as much travel. 

654
00:39:37,900 --> 00:39:42,700
Not nearly as much trouble. 
Our project load was increased, 

655
00:39:42,700 --> 00:39:47,500
and I think it's just that, you 
know, It's probably a natural 

656
00:39:47,500 --> 00:39:51,600
progression that information 
security and therefore I am is 

657
00:39:51,600 --> 00:39:56,400
becoming more and more on the 
front burner of it. 

658
00:39:56,400 --> 00:40:01,600
Budgets and organizations are 
needing help to, you know, 

659
00:40:02,100 --> 00:40:06,100
improve their security posture, 
improve their management of who 

660
00:40:06,100 --> 00:40:10,000
gets access to what. 
So I'm not hoping that 2021 

661
00:40:11,200 --> 00:40:15,000
necessarily slows down on that 
front but I would like to be 

662
00:40:15,000 --> 00:40:17,600
able to take a few Vacations, I 
guess if you will. 

663
00:40:17,600 --> 00:40:21,800
So hopefully everybody has an 
opportunity to kind of recharge 

664
00:40:21,800 --> 00:40:27,400
and blasted the 2021. 
And then also, you know, 

665
00:40:27,700 --> 00:40:33,200
constantly looking to 
communicate with our listeners 

666
00:40:33,200 --> 00:40:37,300
and anybody who's following the 
podcast, please connect on 

667
00:40:37,300 --> 00:40:41,100
LinkedIn, you know. 
Share your ideas for what you 

668
00:40:41,100 --> 00:40:44,400
like hearing about, even what 
you don't want to hear about any

669
00:40:44,400 --> 00:40:47,800
more. 
Stations for guests for future 

670
00:40:47,800 --> 00:40:51,000
podcasts, or open all that. 
But definitely, please send 

671
00:40:51,000 --> 00:40:53,500
LinkedIn connections of unless 
the network. 

672
00:40:53,500 --> 00:40:55,400
Yeah, definitely. 
This is a show, you know, for 

673
00:40:55,400 --> 00:40:58,500
the People by the people. 
And we want to make sure that 

674
00:40:58,500 --> 00:41:00,300
the topics were covering our 
what's interesting out there. 

675
00:41:00,300 --> 00:41:04,400
So if you've got ideas 
suggestions feedback criticism 

676
00:41:04,400 --> 00:41:06,700
whatever maybe send it all our 
way and you know, we're happy to

677
00:41:06,700 --> 00:41:11,400
take it and you know improve and
get better out bad at this and 

678
00:41:11,400 --> 00:41:13,800
hopefully may you continue to 
make the show grow and get 

679
00:41:13,800 --> 00:41:15,800
better topics and or more 
interesting topic. 

680
00:41:15,900 --> 00:41:17,900
You know, over time and folks 
like that. 

681
00:41:17,900 --> 00:41:19,800
So I think that's a good way to 
end it. 

682
00:41:19,800 --> 00:41:23,100
You know, I think I'll be glad 
to see 20/20 kind of in the 

683
00:41:23,100 --> 00:41:26,300
rearview mirror and start start 
fresh again in 21. 

684
00:41:26,800 --> 00:41:30,500
I hope that everyone enjoys the 
holidays again will be taking a 

685
00:41:30,508 --> 00:41:34,200
few weeks break here and we back
in, you know, early mid January 

686
00:41:34,200 --> 00:41:37,900
thing with with another round of
identity and access management 

687
00:41:37,900 --> 00:41:40,300
talk. 
So with that happy Holidays, 

688
00:41:40,400 --> 00:41:44,200
happy New Year and we'll talk 
with you all next year. 

689
00:41:47,700 --> 00:41:51,000
You've been listening to the 
identity at the center podcast, 

690
00:41:51,100 --> 00:41:53,800
if you like what you heard, 
don't forget to subscribe and 

691
00:41:53,800 --> 00:41:57,100
visit us on the web at identity 
at the center.com. 

692
00:41:47,700 --> 00:41:51,000
You've been listening to the 
identity at the center podcast, 

693
00:41:51,100 --> 00:41:53,800
if you like what you heard, 
don't forget to subscribe and 

694
00:41:53,800 --> 00:41:57,100
visit us on the web at identity 
at the center.com.