1
00:00:09,700 --> 00:00:13,000
You're listening to the identity
of the center podcast, this is 

2
00:00:13,000 --> 00:00:15,600
the show that talks about 
identity and access management 

3
00:00:15,700 --> 00:00:18,600
and making sure you know who has
access to what let's get 

4
00:00:18,600 --> 00:00:25,100
started. 
Welcome to the identity at the 

5
00:00:25,100 --> 00:00:27,000
center podcast I'm Jeff and 
that's Jim. 

6
00:00:27,000 --> 00:00:30,700
Hey Jim hey, Jeff, how are you? 
Oh, not so bad yourself. 

7
00:00:30,900 --> 00:00:34,900
I'm doing pretty good. 
So crazy week of business 

8
00:00:34,900 --> 00:00:37,900
travel. 
Of course, right. 

9
00:00:37,900 --> 00:00:43,200
Prior to going on, all those 
trips, I put a contract in on a 

10
00:00:43,200 --> 00:00:46,200
house, right? 
So made a purchase offer was 

11
00:00:46,200 --> 00:00:49,800
accepted. 
And when I was looking at the 

12
00:00:49,800 --> 00:00:53,100
house, I asked the question 
doesn't have high speed 

13
00:00:53,100 --> 00:00:55,300
internet. 
The answer was yes. 

14
00:00:55,300 --> 00:00:57,200
Yeah, no problem. 
I looked around. 

15
00:00:57,200 --> 00:01:01,900
I mean the the house had TVs had
no satellite dishes but now that

16
00:01:01,900 --> 00:01:06,100
I've looked into it further, it 
appears there's there's no 

17
00:01:06,900 --> 00:01:10,200
connectivity from fiber 
perspective like eighteen. 

18
00:01:10,200 --> 00:01:13,700
T Xfinity doesn't run all the 
way to the house. 

19
00:01:14,100 --> 00:01:17,900
So I'm kind of thinking right 
now that Broadband is not going 

20
00:01:17,900 --> 00:01:22,000
to be available. 
The more I looked into satellite

21
00:01:22,000 --> 00:01:25,500
internet, it doesn't look like 
Good option unless you're with 

22
00:01:25,500 --> 00:01:30,900
starlink, which is the Elon Musk
satellite internet. 

23
00:01:30,900 --> 00:01:32,900
And actually, I talked to 
somebody this weekend. 

24
00:01:32,900 --> 00:01:34,900
Jeremiah, if you're listening, 
thank you. 

25
00:01:35,800 --> 00:01:38,400
That has started link instead, 
it's fantastic. 

26
00:01:38,400 --> 00:01:43,700
You can do video calls on, it 
loves it, but it's not like you 

27
00:01:43,700 --> 00:01:47,200
just order it and it shows up in
your on it, especially, you 

28
00:01:47,200 --> 00:01:51,100
know, kind of in the 
Southeastern us. 

29
00:01:52,500 --> 00:01:56,900
So I might I have to actually 
have to cancel the contract 

30
00:01:56,900 --> 00:01:58,900
which would really stink. 
That's killer. 

31
00:01:58,900 --> 00:02:03,400
When you find a nice house like 
that, I totally emphasis M and 

32
00:02:03,400 --> 00:02:07,400
precise and agree because, you 
know, I just moved as well and 

33
00:02:07,400 --> 00:02:10,000
that was like a deal breaker for
me, like we told the realtor 

34
00:02:10,000 --> 00:02:11,800
Mike has to have high speed 
internet. 

35
00:02:11,800 --> 00:02:14,900
Like I'm not, I'm not willing to
compromise on that, there are 

36
00:02:14,900 --> 00:02:18,800
things I will but high speed 
during it was one needs to be, 

37
00:02:18,800 --> 00:02:21,300
you know, gig speed. 
Preferably and fortunately, the 

38
00:02:21,300 --> 00:02:24,400
place we have here is good and I
do have Speed. 

39
00:02:24,400 --> 00:02:29,900
But I mean if this we're talking
2022 this should be a service 

40
00:02:29,900 --> 00:02:34,200
that is like a no brainer and 
certainly certain homes haven't 

41
00:02:34,800 --> 00:02:36,400
been able to keep up with that 
for any number of reasons, 

42
00:02:36,400 --> 00:02:37,700
right? 
Could it's probably not the 

43
00:02:37,700 --> 00:02:40,200
homeowners fault, it's more 
like, just the, the Broadband 

44
00:02:40,200 --> 00:02:42,100
infrastructure has a kind of 
reached that point of 

45
00:02:42,100 --> 00:02:44,800
saturation. 
Yeah, saturation yet, the 

46
00:02:44,808 --> 00:02:46,600
Starling captions pretty 
interesting, though. 

47
00:02:46,800 --> 00:02:49,700
I think the, the issue that I've
had with satellite internet over

48
00:02:49,700 --> 00:02:54,200
the years has been the latency 
which isn't great for Obviously 

49
00:02:54,200 --> 00:02:59,000
gaming, but voice conversations 
and video calls and obviously 

50
00:02:59,000 --> 00:03:02,400
the stuff that you and I do for 
the podcast, relies on that 

51
00:03:02,400 --> 00:03:04,500
quite a bit. 
I'd be interested to see how the

52
00:03:04,500 --> 00:03:08,100
starlink option works. 
I know that it's maybe a little 

53
00:03:08,100 --> 00:03:12,400
bit expensive, but if that's the
only option that is tenable 

54
00:03:12,500 --> 00:03:14,900
then, who knows. 
Maybe it's maybe, it's the right

55
00:03:14,900 --> 00:03:15,800
way to go. 
I don't know. 

56
00:03:16,500 --> 00:03:20,800
I mean, you know what's what's 
more important is it that the 

57
00:03:20,800 --> 00:03:24,700
high-speed internet or is it, is
it the house or Well, I mean, 

58
00:03:24,700 --> 00:03:27,400
the high-speed internet is how I
make my money, so I can't afford

59
00:03:27,400 --> 00:03:29,900
to live in the house without 
high speed internet. 

60
00:03:29,900 --> 00:03:34,900
So it's it's kind of a catch-22.
The funny thing is, I mean, it's

61
00:03:34,900 --> 00:03:38,400
not like this house is in the, 
you know, the middle of nowhere.

62
00:03:38,400 --> 00:03:44,400
It's apparently a Teensy fiber 
and Comcast run to within a 

63
00:03:44,408 --> 00:03:47,400
couple hundred yards of the 
driveway right. 

64
00:03:47,400 --> 00:03:49,800
There they go. 
Down that street, they only run 

65
00:03:49,800 --> 00:03:53,200
into as far as somebody who's on
the street orders. 

66
00:03:53,200 --> 00:03:55,100
It has to Connected into their 
house. 

67
00:03:55,300 --> 00:03:57,900
But can you imagine calling 
either one either? 

68
00:03:57,900 --> 00:04:01,100
One of those companies 18z or 
Comcast and trying to explain it

69
00:04:01,100 --> 00:04:05,300
to a level one support engineer 
that you need somebody to come 

70
00:04:05,300 --> 00:04:07,700
out and extend the service to 
your house. 

71
00:04:07,900 --> 00:04:11,400
So, you know, being that I don't
even have the house and can't 

72
00:04:11,400 --> 00:04:16,600
even place the order yet, right?
I don't know. 

73
00:04:17,100 --> 00:04:21,899
It might just be too expensive 
of a risk to take and the 

74
00:04:21,899 --> 00:04:23,700
startling sounds like it'll be 
available. 

75
00:04:23,800 --> 00:04:28,000
See, I kind of feel like you're 
talking to Jeremiah with his 

76
00:04:28,000 --> 00:04:34,200
experience, like if I could get 
starlink, I think I would take 

77
00:04:34,200 --> 00:04:39,300
the risk that that's going to 
work but, you know, it doesn't 

78
00:04:39,300 --> 00:04:42,000
even sound like that's an option
until next year. 

79
00:04:42,000 --> 00:04:45,500
Maybe not. 
I found a Reddit topic, we're 

80
00:04:45,500 --> 00:04:49,500
about a year ago. 
People that aren't that far from

81
00:04:49,500 --> 00:04:53,900
this new address actually got 
star like but it seems Like 

82
00:04:53,900 --> 00:04:57,000
everybody who got it. 
Never went on to post on how 

83
00:04:57,000 --> 00:05:00,000
good it was. 
So it's like, yeah. 

84
00:05:00,000 --> 00:05:02,600
It got my, I got my 
confirmation. 

85
00:05:02,600 --> 00:05:05,100
That my dish is on the way and 
that was it. 

86
00:05:05,100 --> 00:05:06,400
That was the end of the 
conversation. 

87
00:05:06,400 --> 00:05:09,800
But I mean, we look with what we
do and we're not the only ones 

88
00:05:10,000 --> 00:05:14,500
we work from home, you have to 
have high speed internet, it's 

89
00:05:14,500 --> 00:05:16,900
got to be reliable. 
Well, maybe I said something 

90
00:05:16,900 --> 00:05:19,700
that if you're listening out 
there, if you're a star link, 

91
00:05:21,300 --> 00:05:23,700
have somebody with starlink 
experience, you know, pink. 

92
00:05:23,900 --> 00:05:27,300
My LinkedIn, I'm sure more data 
points would probably help them 

93
00:05:27,300 --> 00:05:28,800
out and look at the website 
right now. 

94
00:05:28,800 --> 00:05:32,200
It says that you get latency as 
low as 20 milliseconds, which is

95
00:05:32,200 --> 00:05:37,600
pretty good. 
Actually, you know, I don't it's

96
00:05:37,600 --> 00:05:38,700
marketing. 
So who knows, right? 

97
00:05:38,700 --> 00:05:43,700
As low as 20 sounds great. 
What is the realistic you know, 

98
00:05:44,500 --> 00:05:46,300
measurement will be much more 
interesting? 

99
00:05:47,200 --> 00:05:51,700
Well, I think if you're under 50
to 100, you're probably ok but 

100
00:05:51,700 --> 00:05:53,600
past that you might have some 
struggles. 

101
00:05:53,800 --> 00:05:55,500
But who knows? 
I don't know if you have 

102
00:05:55,500 --> 00:05:58,600
starlink experience in the real 
world ping Jim. 

103
00:05:58,700 --> 00:06:01,600
I'm sure you know, good or bad, 
he would appreciate it. 

104
00:06:01,600 --> 00:06:06,000
Yeah, I would and I know people 
don't tune into a Denny's, the 

105
00:06:06,000 --> 00:06:08,300
center podcast, he ever met all 
my problems. 

106
00:06:08,600 --> 00:06:11,800
But imagine this also is that 
the folks in the house. 

107
00:06:11,800 --> 00:06:16,800
Now tell me that they have a, 
and t, and t DSL, which doesn't 

108
00:06:16,800 --> 00:06:20,300
sound good enough, right? 
But it's worth investigating. 

109
00:06:20,700 --> 00:06:24,200
When I called AT&T, they said, 
sorry, we can't read dies, That 

110
00:06:24,200 --> 00:06:27,000
address. 
So somebody's lying. 

111
00:06:28,100 --> 00:06:32,300
Yeah, there are other houses out
there, I guess. 

112
00:06:32,300 --> 00:06:36,100
But yeah, first world problem 
but of extreme importance for 

113
00:06:36,100 --> 00:06:38,000
you and I based on kind of what 
we do for a living. 

114
00:06:38,000 --> 00:06:41,600
So for sure. 
Absolutely What else we got 

115
00:06:41,600 --> 00:06:43,800
going on? 
We got Gartner coming up in 

116
00:06:43,800 --> 00:06:46,600
August's you and I are going to 
be there, we're going to be 

117
00:06:46,600 --> 00:06:48,500
there. 
We're going to be podcasting, 

118
00:06:49,600 --> 00:06:54,600
the more of our listeners who 
can link up with us because we'd

119
00:06:54,600 --> 00:06:58,200
love to get people on to spend 5
10 minutes with us. 

120
00:06:58,200 --> 00:07:01,600
Just telling us about you know, 
what sessions they've been to 

121
00:07:01,600 --> 00:07:04,400
what was their favor session. 
What would their big takeaways? 

122
00:07:04,800 --> 00:07:08,400
I think if we can compile a few 
of those things into you know 

123
00:07:08,400 --> 00:07:12,900
some episodes be great In we 
haven't figured out our whole 

124
00:07:12,900 --> 00:07:16,600
strategy but, you know, based on
the authenticate conference that

125
00:07:18,000 --> 00:07:20,700
I ditched you for, because I had
covid. 

126
00:07:20,700 --> 00:07:22,400
So I didn't really I will never 
let you live it down. 

127
00:07:22,400 --> 00:07:26,800
Never let me live it down covid 
or not you know you you had an 

128
00:07:26,800 --> 00:07:31,200
episode per day and I'd love to 
match that if possible. 

129
00:07:31,600 --> 00:07:33,800
Yeah, it's a lot of work but I 
think we could kind of cool. 

130
00:07:33,800 --> 00:07:37,600
I'm I'm still trying to work out
where we will do the podcasting.

131
00:07:37,600 --> 00:07:40,500
We've got a lead on a spot 
that's like one level up. 

132
00:07:40,800 --> 00:07:44,000
But there's conversations 
between like Gartner and Caesars

133
00:07:44,000 --> 00:07:45,500
and approvals and also their 
stuff. 

134
00:07:45,500 --> 00:07:48,400
So hopefully we get that kind of
sorted out sooner rather than 

135
00:07:48,400 --> 00:07:50,200
later. 
But, you know, my thought was 

136
00:07:50,200 --> 00:07:51,900
like, yeah, let's let's talk to 
folks, we're going to be out 

137
00:07:51,900 --> 00:07:54,900
there and if you want to be on 
the show, great, we can work it 

138
00:07:54,900 --> 00:07:55,900
out. 
Even if you just kind of want to

139
00:07:55,900 --> 00:08:01,000
watch the magic happen as boring
as it might be, you know, maybe 

140
00:08:01,000 --> 00:08:02,900
even being in the room while we 
record with others. 

141
00:08:02,900 --> 00:08:04,400
You know, I think that's 
certainly an opportunity as well

142
00:08:04,400 --> 00:08:06,900
but at the very least you know, 
give us the opportunity to kind 

143
00:08:06,900 --> 00:08:09,300
of give a fist bump of thanks, 
that people are going to be out 

144
00:08:09,300 --> 00:08:11,500
there, listening or who are 
listening We're going to be at 

145
00:08:11,500 --> 00:08:14,400
Gartner. 
We're always happy to meet up 

146
00:08:14,400 --> 00:08:17,200
and kind of have conversations 
and stuff like that. 

147
00:08:17,200 --> 00:08:20,200
I think that would be really 
cool and this is the first time,

148
00:08:20,200 --> 00:08:23,400
you know, Jim and I will be at 
the same conference and multiple

149
00:08:23,400 --> 00:08:26,100
years and I have been on the 
road pretty much all week this 

150
00:08:26,100 --> 00:08:28,100
week. 
Saw each other for the first 

151
00:08:28,100 --> 00:08:33,799
time on Monday last Monday in 
over two years which was, you 

152
00:08:33,799 --> 00:08:37,200
know, a little bit surreal. 
But yeah, here we are, you know,

153
00:08:37,200 --> 00:08:40,900
we video like every week we 
visited every week for the The 

154
00:08:40,900 --> 00:08:45,400
last two years so it wasn't like
oh that's a big surprise what 

155
00:08:45,400 --> 00:08:49,500
you look like now. 
But yeah it was it was 

156
00:08:49,500 --> 00:08:51,600
definitely weird. 
It was my first business trip in

157
00:08:51,600 --> 00:08:54,100
over two years. 
Well, that's back baby. 

158
00:08:54,200 --> 00:08:59,100
We're all over the place now. 
So I guess good times we were 

159
00:08:59,108 --> 00:09:02,400
having some conversations this 
week to that about some some 

160
00:09:02,400 --> 00:09:04,500
cool stuff that we're working on
that. 

161
00:09:04,600 --> 00:09:07,400
Not ready to announce yet but 
stay tuned for latest year. 

162
00:09:07,400 --> 00:09:11,400
We'll keep some mystery around 
it but the calm Two things like 

163
00:09:11,400 --> 00:09:12,700
that. 
One of the conversations was, 

164
00:09:12,700 --> 00:09:15,600
we're kind of talking about the 
podcasts folks and well, 

165
00:09:16,900 --> 00:09:18,100
Clinton. 
If you're listening I'm going to

166
00:09:18,100 --> 00:09:20,100
steal this because like, you 
know, how you guys come up with 

167
00:09:20,100 --> 00:09:23,300
ideas and we kind of explained 
our process, which sometimes 

168
00:09:23,300 --> 00:09:26,300
it's plans, sometimes, it's not,
here we are. 

169
00:09:26,500 --> 00:09:28,600
We've been on the road all week,
I've had chances chance to sit 

170
00:09:28,600 --> 00:09:33,800
down, and it's Saturday, July 
23rd, and we're recording this. 

171
00:09:33,800 --> 00:09:35,900
And I'm going to have to get it,
edited and ready to go and 

172
00:09:35,900 --> 00:09:37,700
publish for early Monday 
morning. 

173
00:09:37,700 --> 00:09:40,700
So that's sort of like the 
process of the magic comes. 

174
00:09:40,800 --> 00:09:43,100
Behind it. 
But you know, a lot of the times

175
00:09:43,100 --> 00:09:46,400
we pull topics from, is what 
happens to us, sort of in the 

176
00:09:46,400 --> 00:09:49,300
real world. 
As we're having conversations, 

177
00:09:49,300 --> 00:09:53,500
you know, with either colleagues
or clients or analysts, whoever 

178
00:09:53,500 --> 00:09:56,400
it may be. 
And the conversation that we 

179
00:09:56,400 --> 00:09:58,500
were having earlier, this week 
was really kind of around like 

180
00:09:58,500 --> 00:10:01,100
this. 
This idea of a hub-and-spoke 

181
00:10:01,100 --> 00:10:05,400
model and I got think Jim 
thinking about mergers and 

182
00:10:05,400 --> 00:10:07,500
Acquisitions. 
I think that's we're going to 

183
00:10:07,508 --> 00:10:12,000
take the conversation today is 
talk about sort of I am in the 

184
00:10:12,000 --> 00:10:14,200
MMA space, mergers, and 
acquisition space. 

185
00:10:14,200 --> 00:10:17,800
But yeah, before you go any 
further, this would be a good 

186
00:10:17,800 --> 00:10:23,900
point to insert the an audio 
clip from the Seinfeld show 

187
00:10:23,900 --> 00:10:27,600
where George is saying it's a 
show about nothing. 

188
00:10:27,600 --> 00:10:30,700
You see this is going to be a 
topic right here. 

189
00:10:30,700 --> 00:10:32,800
It's about nothing rocket about 
nothing. 

190
00:10:32,800 --> 00:10:35,500
For you talk about mergers and 
Acquisitions and thing and 

191
00:10:35,500 --> 00:10:40,200
challenges and opportunities in 
the identity space, that those 

192
00:10:40,200 --> 00:10:41,000
might present. 
Aunt. 

193
00:10:41,300 --> 00:10:45,100
But yes. 
Yeah I think in the spirit of 

194
00:10:45,100 --> 00:10:47,200
Seinfeld, I don't want to get a 
copyright strike but just 

195
00:10:47,200 --> 00:10:52,300
imagine you know the show about 
nothing but instead were about 

196
00:10:52,300 --> 00:10:53,700
identity, nothing. 
I don't know if that makes sense

197
00:10:53,700 --> 00:10:56,500
or not. 
Yeah, I get it. 

198
00:10:56,900 --> 00:10:59,100
Everyone gets it. 
All right, let's talk about 

199
00:10:59,100 --> 00:11:02,300
mergers and Acquisitions. 
I guess the way that you and I 

200
00:11:02,300 --> 00:11:04,600
were kind of thinking about this
was sort of like talk about 

201
00:11:04,600 --> 00:11:06,700
maybe some of the challenges 
that first and maybe some of the

202
00:11:06,700 --> 00:11:10,000
opportunities and I know what 
divestitures is a thing out 

203
00:11:10,000 --> 00:11:12,100
there as well. 
We'll probably kind of weave 

204
00:11:12,100 --> 00:11:15,900
that towards the end, but maybe 
from just, let's just talk ma 

205
00:11:15,900 --> 00:11:18,400
for right now. 
I guess, what are some of the 

206
00:11:18,400 --> 00:11:20,800
things that you think about 
formica challenge perspective, 

207
00:11:20,800 --> 00:11:24,100
that folks who were in the 
identity space living in the 

208
00:11:24,100 --> 00:11:28,600
trenches, in the real world 
should probably start to think 

209
00:11:28,600 --> 00:11:32,900
about or at least consider if 
they're about to go through some

210
00:11:32,900 --> 00:11:37,000
sort of m&a activity? 
Yeah, I mean, while I think that

211
00:11:37,000 --> 00:11:41,100
the Mna activity kind of needs 
further Mission. 

212
00:11:41,100 --> 00:11:43,900
Right? 
Because there could be the M 

213
00:11:43,900 --> 00:11:47,700
which is mergers and it could be
kind of a merger of equals re. 

214
00:11:47,700 --> 00:11:51,700
So a big bank is joining with 
another big bank or whatever 

215
00:11:51,700 --> 00:11:57,100
industry, but you've kind of got
to organizations that are 

216
00:11:57,400 --> 00:12:00,700
roughly the same size or have 
roughly the same Sway. 

217
00:12:01,000 --> 00:12:05,200
And you've got to kind of like 
Stitch those two together, 

218
00:12:05,600 --> 00:12:08,900
whereas on the Acquisitions, 
that I think of a bigger fish, 

219
00:12:08,900 --> 00:12:12,500
consuming of smaller fish, In 
other words, a big company 

220
00:12:13,000 --> 00:12:15,800
buying out a smaller company. 
In this smaller company is going

221
00:12:15,800 --> 00:12:20,900
to plug into, you know, how 
things are done at the bigger 

222
00:12:20,900 --> 00:12:25,400
company. 
I also kind of feel like 

223
00:12:25,400 --> 00:12:29,700
especially in that second 
scenario is if your company's 

224
00:12:29,700 --> 00:12:33,600
done a lot of pre-planning or 
requires companies all the time,

225
00:12:34,300 --> 00:12:39,200
you prop, you really should kind
of start to have a strategy for 

226
00:12:39,600 --> 00:12:42,300
how you fit. 
It in an acquired company, 

227
00:12:42,300 --> 00:12:44,200
right? 
So there's the policies and 

228
00:12:44,208 --> 00:12:46,900
standards and all the things 
that you're going to adopt and 

229
00:12:46,900 --> 00:12:51,300
that we have a strategy for how 
we handle, you know, active 

230
00:12:51,300 --> 00:12:54,200
directory or single sign on 
things like that. 

231
00:12:55,400 --> 00:13:00,400
So I think that that definition 
really is a good starting point,

232
00:13:00,600 --> 00:13:05,400
merger, I think, is it 
definitely has its challenges. 

233
00:13:05,400 --> 00:13:08,800
It also has presents a lot of 
opportunities as well, because 

234
00:13:08,800 --> 00:13:15,300
potentially the company, Merging
with brings as much good stuff 

235
00:13:15,300 --> 00:13:17,700
to the table as your 
organization, or maybe more. 

236
00:13:18,600 --> 00:13:21,300
Yeah, I guess, from a. 
So, let's the mergers and 

237
00:13:21,308 --> 00:13:26,100
acquisition definition is 
flexible, because you could be 

238
00:13:26,100 --> 00:13:29,500
on either side and of those in 
any capacity, right? 

239
00:13:29,500 --> 00:13:33,400
If you're doing a merger, 
Chances are you know 

240
00:13:33,400 --> 00:13:35,100
organization probably the same 
size. 

241
00:13:35,300 --> 00:13:37,500
There might not be a bigger fish
or maybe there is a bigger fish,

242
00:13:37,500 --> 00:13:38,600
right? 
Who's going to be in charge, is 

243
00:13:38,600 --> 00:13:41,700
one of the things that I think 
about is, okay, to organizations

244
00:13:41,700 --> 00:13:45,300
of equal stature and capability,
right? 

245
00:13:45,300 --> 00:13:49,500
Who becomes the dominant 
personality from an identity 

246
00:13:49,500 --> 00:13:53,100
perspective, when it comes 
through that merger in the case 

247
00:13:53,100 --> 00:13:57,900
of an acquisition, if you are 
acquiring someone else, chances 

248
00:13:57,900 --> 00:14:01,800
are, you're probably going to, 
you know, impose your Any 

249
00:14:01,800 --> 00:14:06,200
practice that processes and 
Technologies onto whoever it is 

250
00:14:06,200 --> 00:14:09,000
that you're requiring. 
Conversely if you are being 

251
00:14:09,000 --> 00:14:13,100
acquired you might have the 
opposite, right? 

252
00:14:13,200 --> 00:14:17,100
The acquiring organization May 
impose certain things upon your 

253
00:14:17,400 --> 00:14:21,600
your identity stack, whether 
it's process or technology that 

254
00:14:21,600 --> 00:14:25,000
need to be accounted for now. 
Doesn't always hold true, right?

255
00:14:25,000 --> 00:14:30,500
It may be that your company's 
acquiring technology or 

256
00:14:30,600 --> 00:14:34,400
acquiring another knee because 
of the success of that 

257
00:14:34,400 --> 00:14:38,300
technology or processes and you 
might be able to impose some of 

258
00:14:38,300 --> 00:14:40,700
the better processes and things 
that come along. 

259
00:14:40,700 --> 00:14:43,700
So I think it's important to not
just look at this and like in a 

260
00:14:43,700 --> 00:14:48,200
black-and-white way and say okay
we are buying you so therefore 

261
00:14:48,200 --> 00:14:51,700
you are going to do it the way 
that we tell you to do it that 

262
00:14:51,700 --> 00:14:54,200
certainly can be the case but 
does not always the case. 

263
00:14:54,700 --> 00:14:58,800
So I think if you've got a good 
identity program of whether 

264
00:14:58,800 --> 00:15:02,800
you're the acquiree or the 
acquirer Um, there is the 

265
00:15:02,800 --> 00:15:06,200
opportunity to kind of extend 
that maturity into the 

266
00:15:06,200 --> 00:15:08,100
organization either up or down 
from there. 

267
00:15:08,600 --> 00:15:10,900
I think some of the other 
challenges I think about too is 

268
00:15:10,900 --> 00:15:14,200
like, you know, you've got 
different it systems that are 

269
00:15:14,200 --> 00:15:17,000
going to be out there. 
So you think about it, okay. 

270
00:15:17,700 --> 00:15:22,600
You know, the the the 
competition of single sign-on of

271
00:15:22,600 --> 00:15:26,000
MFA of the different 
directories, you know, who's 

272
00:15:26,000 --> 00:15:27,900
going to, how we're going to 
handle those things, are they 

273
00:15:27,900 --> 00:15:30,100
going to be Consolidated or they
get a kept separate? 

274
00:15:30,500 --> 00:15:32,800
You know, I think the idea 
Allstate is a lot of folks like 

275
00:15:32,800 --> 00:15:35,700
okay well you know, we're going 
to be one big happy family with 

276
00:15:35,700 --> 00:15:40,900
one giant SSO, 11 MFA solution 
and one directory and then the 

277
00:15:40,900 --> 00:15:44,300
real world hits and you realize 
oh you know here we are five 

278
00:15:44,300 --> 00:15:47,800
years later and we have 48 
active directory domains because

279
00:15:47,800 --> 00:15:50,800
we never Winters observe you 
know consolidation or you may 

280
00:15:50,800 --> 00:15:53,300
know Jim you and I we could have
seen that you know multiple 

281
00:15:53,300 --> 00:15:56,500
times over the years and there 
was never like any steps to sort

282
00:15:56,500 --> 00:15:58,600
of like think about this 
strategically. 

283
00:15:58,600 --> 00:16:00,800
It was we've just gotta make it 
work. 

284
00:16:00,800 --> 00:16:03,600
So okay. 
Slap the domain in there, we'll 

285
00:16:03,600 --> 00:16:06,800
just create a forest and set up 
the trust and we're done. 

286
00:16:06,800 --> 00:16:08,100
We wash. 
You kind of like move on to the 

287
00:16:08,108 --> 00:16:10,300
next thing. 
So those are some of the things 

288
00:16:10,300 --> 00:16:12,200
I think about as well. 
Any thoughts on what? 

289
00:16:12,200 --> 00:16:15,700
I just touched on? 
Yeah, yeah, I actually was 

290
00:16:15,700 --> 00:16:18,800
thinking about, you know, what 
we're really talking about is 

291
00:16:18,800 --> 00:16:22,700
like the full on integration of 
the acquired company. 

292
00:16:24,100 --> 00:16:28,100
And I think one thing that kind 
of has to be laid out is that 

293
00:16:28,200 --> 00:16:29,700
it's not going to happen 
overnight. 

294
00:16:29,700 --> 00:16:32,400
There's not going to be a 
flipping of the switch and the 

295
00:16:32,400 --> 00:16:35,900
company's fully integrated. 
So there probably are steps 

296
00:16:35,900 --> 00:16:38,500
along the way. 
Usually it starts with things 

297
00:16:38,500 --> 00:16:42,000
like the email system. 
Let's get the email system, it 

298
00:16:42,000 --> 00:16:44,100
see everybody under one email 
system. 

299
00:16:45,500 --> 00:16:50,600
Federation is usually an I am 
solution that has put into place

300
00:16:50,600 --> 00:16:55,600
so that people can, you know, 
authenticate and and reach 

301
00:16:55,700 --> 00:16:58,100
corporate applications of the 
acquiring company. 

302
00:16:58,500 --> 00:17:03,000
Sometimes people are just moved 
over at the A swollen of you can

303
00:17:03,000 --> 00:17:06,700
just migrate the users over 
into, you know, a new active 

304
00:17:06,700 --> 00:17:10,500
directory, or new single sign-on
system and, you know, get rid of

305
00:17:10,500 --> 00:17:15,300
some of the old it systems. 
But that in my experience is 

306
00:17:15,300 --> 00:17:18,400
usually the scenario where a 
much bigger company requires a 

307
00:17:18,400 --> 00:17:21,700
much smaller company and it's 
like resources are thrown Outta 

308
00:17:21,700 --> 00:17:26,599
to make all the old it systems 
of the acquired company, just go

309
00:17:26,599 --> 00:17:29,400
away. 
But in a scenario where that 

310
00:17:29,400 --> 00:17:34,100
acquired company has it Systems 
that are going to come over and 

311
00:17:34,100 --> 00:17:38,200
continue to be used. 
Now, you've got a different set 

312
00:17:38,200 --> 00:17:40,100
of. 
I am challenges in other words, 

313
00:17:40,300 --> 00:17:43,800
how did, what's the transition 
state then once the final State 

314
00:17:43,800 --> 00:17:46,600
and into something that you were
talking about, is what we've 

315
00:17:46,600 --> 00:17:49,700
seen so many times with clients 
that we've worked with where 

316
00:17:50,100 --> 00:17:53,200
they get so far with the 
integration and then they move 

317
00:17:53,200 --> 00:17:56,200
on to other things. 
It's like somebody just kind of 

318
00:17:56,200 --> 00:18:02,100
gave up on it or there wasn't 
the executive push and I That's 

319
00:18:02,700 --> 00:18:06,900
that's kind of one of the things
I've learned through the ma and 

320
00:18:06,900 --> 00:18:10,400
divestiture activity that I've 
been involved with is that 

321
00:18:10,500 --> 00:18:17,100
trying to drive integration of 
it and infosec. 

322
00:18:17,100 --> 00:18:21,600
And I am from a Grassroots 
level, is, is almost assure 

323
00:18:21,600 --> 00:18:25,300
loser, especially when it gets 
to Major Integrations, like, 

324
00:18:25,300 --> 00:18:28,400
hey, we the acquired company has
their own active directory. 

325
00:18:28,400 --> 00:18:32,700
So, let's say that the acquired 
A company is like a third of the

326
00:18:32,700 --> 00:18:35,400
size of the acquirer so it's not
a small company. 

327
00:18:35,400 --> 00:18:39,000
It's you know, say hundreds or 
thousands of users and there's 

328
00:18:39,000 --> 00:18:42,300
an active directory and 
applications integrated into act

329
00:18:42,300 --> 00:18:45,300
active directory. 
You're going to have a hard time

330
00:18:45,500 --> 00:18:50,800
if you are the active directory,
team of the acquirer to convince

331
00:18:51,600 --> 00:18:56,400
the active directory, team of 
the acquiree, to give up their 

332
00:18:56,400 --> 00:18:59,300
control and move everything into
a central active directory. 

333
00:18:59,500 --> 00:19:05,200
However, if from like a sea, Yo 
level, you've got the support to

334
00:19:05,400 --> 00:19:09,700
miss support the direction and 
and the mandate to get down to 

335
00:19:09,700 --> 00:19:12,700
one active directory, you got to
make it happen. 

336
00:19:12,700 --> 00:19:16,100
Everybody's had a March of that 
tune or, you know, they might 

337
00:19:16,100 --> 00:19:20,600
not be happy here anymore, but 
ultimately, I think that, you 

338
00:19:20,608 --> 00:19:23,200
know, if the mindset is, we're 
going to build a better 

339
00:19:23,200 --> 00:19:26,800
mousetrap in my experience. 
That's a loser. 

340
00:19:27,200 --> 00:19:30,200
You know, you've got to do more 
than build a better mousetrap, 

341
00:19:30,400 --> 00:19:33,500
you've got to have The Mandate? 
Yeah degree. 

342
00:19:33,500 --> 00:19:39,000
I think you know, we talked 
about sort of like treating, a 

343
00:19:39,000 --> 00:19:43,200
technology implementation is 
like an opportunity to do 

344
00:19:43,200 --> 00:19:46,500
process re-engineering, and I 
kind of see the same thing 

345
00:19:46,500 --> 00:19:52,400
around mergers and Acquisitions 
is sometimes it's the right 

346
00:19:52,400 --> 00:19:52,900
time. 
I do it. 

347
00:19:52,900 --> 00:19:58,000
Sometimes it's not, if you have 
a modern mature identity 

348
00:19:58,000 --> 00:20:02,900
program, You know, the the 
inclusion of just another Target

349
00:20:02,900 --> 00:20:06,800
or another system, to manage, 
generally should fall in line 

350
00:20:06,800 --> 00:20:09,500
with whatever the program is 
already established for like a 

351
00:20:09,500 --> 00:20:12,300
standard integration pattern 
perspective. 

352
00:20:12,300 --> 00:20:17,900
For example, it's it's more 
complicated but it should fall 

353
00:20:17,900 --> 00:20:20,900
into that same thing. 
What I think typically happens 

354
00:20:20,900 --> 00:20:24,400
though is most I am programs are
not that mature and so they're 

355
00:20:24,400 --> 00:20:26,000
left scrambling and trying to 
figure out. 

356
00:20:26,000 --> 00:20:28,800
Okay well how are we going to 
get you know this new population

357
00:20:28,800 --> 00:20:30,800
in? 
So our system are they going to 

358
00:20:30,800 --> 00:20:34,200
go into the EHR platform? 
If they are, is there any 

359
00:20:34,200 --> 00:20:37,700
automation that is going to be 
used to sort of create new 

360
00:20:37,700 --> 00:20:39,800
accounts, for those individuals 
coming in? 

361
00:20:41,300 --> 00:20:44,400
You know, how is, how are people
going to get access to the 

362
00:20:44,400 --> 00:20:46,500
ticketing system to submit 
requests, right? 

363
00:20:46,500 --> 00:20:48,500
How are we going to get them? 
Their IDs and passwords. 

364
00:20:49,100 --> 00:20:53,500
My experience is has been, it's 
a pretty manual process where 

365
00:20:53,500 --> 00:20:56,500
there are spreadsheets of IDs 
and passwords that get kind of 

366
00:20:56,500 --> 00:20:59,100
passed around and sent to some 
coordinator. 

367
00:20:59,400 --> 00:21:02,700
Of the of the activity, right to
get off to managers and things 

368
00:21:02,700 --> 00:21:07,000
like that. 
But it's not great and trying to

369
00:21:07,000 --> 00:21:09,800
design it at the same time, 
you're doing the acquisition. 

370
00:21:10,100 --> 00:21:11,900
I feel is a losing proposition 
as well. 

371
00:21:12,900 --> 00:21:15,800
Yeah, you know, one other 
thought as you were talking it 

372
00:21:15,800 --> 00:21:23,000
got me got me thinking about was
the reason why companies go out 

373
00:21:23,000 --> 00:21:29,100
and acquire other companies and 
perform mergers is that They 

374
00:21:29,100 --> 00:21:32,700
think that the money that's 
being made by the acquired 

375
00:21:32,700 --> 00:21:36,900
company, we can make more money.
They were to leverage what we 

376
00:21:36,900 --> 00:21:39,100
have. 
So it's leverage our, it 

377
00:21:39,100 --> 00:21:42,600
systems, leverage all of our 
back-office, maybe leverage our 

378
00:21:42,600 --> 00:21:46,400
manufacturing capabilities, 
leverage, our sales force, 

379
00:21:46,400 --> 00:21:50,500
things like that. 
And so the idea is that, you 

380
00:21:50,500 --> 00:21:54,300
know, we want to acquire this, 
the company what they're good 

381
00:21:54,300 --> 00:21:58,000
at, but we want to leverage what
we have because we think it's 

382
00:21:58,100 --> 00:22:05,100
can make it Much better company 
when I think about that mindset 

383
00:22:05,100 --> 00:22:07,100
and I think about running a back
office. 

384
00:22:07,100 --> 00:22:10,100
Not just the back office. 
But hey, let's say we start 

385
00:22:10,100 --> 00:22:13,300
manufacturing these goods and 
different facilities and things 

386
00:22:13,300 --> 00:22:16,500
like that. 
The idea of identity management,

387
00:22:16,500 --> 00:22:19,500
it kind of like goes all the way
back to identity management. 

388
00:22:19,500 --> 00:22:23,500
Like if you can't even log in 
and get from system to system, 

389
00:22:23,500 --> 00:22:26,900
or you keep running into access 
denied because their systems 

390
00:22:26,900 --> 00:22:30,200
aren't fully integrated Or else 
not even use the term 

391
00:22:30,200 --> 00:22:32,500
integrated. 
But like, the vision should be 

392
00:22:32,500 --> 00:22:36,100
that we're kind of getting to 
just one set of systems for the 

393
00:22:36,100 --> 00:22:39,200
company. 
If you, if you can't get the, I 

394
00:22:39,200 --> 00:22:43,100
am stuff straightened out. 
Everything else is going to 

395
00:22:43,100 --> 00:22:46,200
suffer. 
And so I kind of feel like, you 

396
00:22:46,200 --> 00:22:51,100
know, from a technology leader 
perspective, getting that, I am 

397
00:22:51,100 --> 00:22:54,600
P straightened out as just of 
the utmost importance and it 

398
00:22:54,700 --> 00:22:59,100
again, if you kind of leave that
to a Grassroots effort, to say, 

399
00:22:59,100 --> 00:23:04,000
alright, well, we don't want to 
rock the boat and force and make

400
00:23:04,000 --> 00:23:07,500
people who are over here, feel 
like, oh no, big brother's 

401
00:23:07,500 --> 00:23:10,100
coming in and forcing me. 
So I'm just going to go from a 

402
00:23:10,108 --> 00:23:13,000
Grassroots perspective. 
My active directory. 

403
00:23:13,000 --> 00:23:16,100
Ministers work out. 
I'm telling you from what I've 

404
00:23:16,100 --> 00:23:18,000
seen, it'll never happen. 
Yeah. 

405
00:23:18,000 --> 00:23:20,800
I think the intention is that 
you know, in every go through 

406
00:23:20,800 --> 00:23:23,900
sort of this process of a merger
acquisition it's to make the 

407
00:23:23,900 --> 00:23:26,000
experience is good for everybody
involved. 

408
00:23:27,200 --> 00:23:30,100
I don't know anybody who likes 
to try to have a process where 

409
00:23:30,100 --> 00:23:31,900
it just doesn't work, but that's
just the way it is. 

410
00:23:32,900 --> 00:23:39,200
The process of merging 
identities is always a challenge

411
00:23:39,200 --> 00:23:41,600
too, because sometimes you'll 
come across these situations. 

412
00:23:41,800 --> 00:23:44,900
Where, you know, people might 
have an account in one 

413
00:23:44,900 --> 00:23:49,200
organization and the 
organization is acquiring them. 

414
00:23:49,200 --> 00:23:50,600
They may have an account there 
as well. 

415
00:23:50,600 --> 00:23:54,000
So trying to kind of pull those 
together is a challenge. 

416
00:23:54,300 --> 00:23:59,400
I've seen it before to where 
people are not necessarily 

417
00:23:59,400 --> 00:24:02,300
loaded into directory systems, 
it might be kind of treated as 

418
00:24:02,300 --> 00:24:06,900
like one-offs and they live sort
of like in this transitive State

419
00:24:07,000 --> 00:24:10,500
between directories or between 
HR platforms, whatever it may 

420
00:24:10,500 --> 00:24:11,700
be. 
So I think that's another thing.

421
00:24:11,800 --> 00:24:14,700
And people kind of consider is 
as you're going through this 

422
00:24:14,700 --> 00:24:16,500
process, right? 
You might have like, on your 

423
00:24:16,500 --> 00:24:19,600
side and identity and access 
management platform that is used

424
00:24:19,600 --> 00:24:25,000
to receiving identity data from 
an HR platform, like a work day 

425
00:24:25,000 --> 00:24:29,000
or an oracle. 
Sure there's tons of them out 

426
00:24:29,000 --> 00:24:32,900
there, right? 
How is your system going to 

427
00:24:32,900 --> 00:24:37,500
respond when that data is not 
available or can't be used for 

428
00:24:37,500 --> 00:24:39,900
whatever reason? 
How are you going to provision? 

429
00:24:39,900 --> 00:24:41,700
Those accounts is always a 
question and the same. 

430
00:24:41,800 --> 00:24:44,300
Thing is, if there is a 
termination, how are you going 

431
00:24:44,300 --> 00:24:47,200
to make sure, you know this kind
of touching on the divestiture 

432
00:24:47,200 --> 00:24:48,500
topic that we'll talk about as 
well. 

433
00:24:48,500 --> 00:24:51,300
But how do you make sure that 
acts as unwind into has been a 

434
00:24:51,300 --> 00:24:53,000
challenge? 
This is where I typically see 

435
00:24:53,000 --> 00:24:57,400
those spreadsheets get passed 
around which stinks and nobody 

436
00:24:57,400 --> 00:25:00,300
likes that. 
So I think if the system is 

437
00:25:00,300 --> 00:25:04,800
designed in a way that again 
from a program perspective is 

438
00:25:04,800 --> 00:25:07,700
okay, it's just another Target. 
Another population to manage 

439
00:25:07,700 --> 00:25:11,100
insert them here and you've got 
sort of like this manual hook 

440
00:25:11,100 --> 00:25:14,000
up. 
For when that RV, you know, 

441
00:25:14,000 --> 00:25:17,400
comes along to the campground, 
kind of them, be more Transit. 

442
00:25:17,400 --> 00:25:20,300
I think it makes more sense. 
So, when you're designing your I

443
00:25:20,300 --> 00:25:24,700
am platform, especially when it 
comes to things like identity, 

444
00:25:24,700 --> 00:25:28,100
governance, and the axis engine 
side of things is making sure 

445
00:25:28,100 --> 00:25:30,500
that you've got not only a happy
path, right? 

446
00:25:30,500 --> 00:25:35,400
Here's your identity source of 
truth, but here's the manual, / 

447
00:25:35,400 --> 00:25:37,700
may be unhappy path. 
Of how are we going to handle 

448
00:25:37,700 --> 00:25:39,600
folks? 
Who don't fit into that? 

449
00:25:39,600 --> 00:25:41,500
Into that bucket? 
What your thoughts? 

450
00:25:41,500 --> 00:25:42,100
Yeah. 
Yeah. 

451
00:25:42,100 --> 00:25:44,600
I mean I'm sitting here 
thinking, probably the first 

452
00:25:44,600 --> 00:25:47,300
time you do, this is going to be
the hardest sale on the 

453
00:25:47,300 --> 00:25:50,000
acquisition track. 
And I was thinking about the 

454
00:25:50,000 --> 00:25:55,300
merger track where a merger of 
equals and you know, I was 

455
00:25:55,300 --> 00:25:57,400
thinking about. 
Okay, so we have say to 

456
00:25:57,400 --> 00:26:00,100
companies with 10,000 employees 
each? 

457
00:26:01,000 --> 00:26:04,700
You know we talked about kind of
it happens, iteration. 

458
00:26:04,700 --> 00:26:07,800
So in other words you put 
together enough Plumbing so that

459
00:26:08,300 --> 00:26:12,100
you can kind of work together 
but that's not the vision of You

460
00:26:12,100 --> 00:26:19,200
know, how you achieve the, The 
Leverage you get from take going

461
00:26:19,200 --> 00:26:20,600
from two companies to one 
company. 

462
00:26:20,600 --> 00:26:25,500
It's by a full-on, you know, 
melding of all this back office.

463
00:26:25,900 --> 00:26:29,600
And I think about things like, 
you know what, if you're using 

464
00:26:29,600 --> 00:26:34,400
the same SAS applications like 
Salesforce or even something, as

465
00:26:34,400 --> 00:26:38,100
simple as concur. 
Now I go to concurred it's 

466
00:26:38,100 --> 00:26:41,100
asking me to login, like which 
one do I use? 

467
00:26:41,100 --> 00:26:44,900
So you can imagine in like the 
cloud brings on all these new 

468
00:26:44,900 --> 00:26:49,600
directories and how you get to 
those and how you authenticate 

469
00:26:49,600 --> 00:26:52,300
to them and how you're being 
provision to them. 

470
00:26:52,500 --> 00:26:55,400
All those things need to be 
taken into account. 

471
00:26:55,400 --> 00:26:59,400
As I think if we just think 
about it from the traditional 

472
00:26:59,400 --> 00:27:03,300
directory perspective of an 
active directory, that's 

473
00:27:03,300 --> 00:27:05,800
complicated enough. 
When you started thinking about 

474
00:27:05,900 --> 00:27:12,800
organizational units and and 
policies, and You know, all the 

475
00:27:12,800 --> 00:27:15,600
things that go with ad and 
merging those together over 

476
00:27:15,600 --> 00:27:19,200
them, when you take all of these
Cloud applications that have 

477
00:27:19,200 --> 00:27:23,000
their own directories, and the 
fact that organizations could be

478
00:27:23,400 --> 00:27:27,700
the merged organizations could 
be using the same application. 

479
00:27:27,700 --> 00:27:31,800
So it requires a extensive 
planning of requires that the 

480
00:27:31,800 --> 00:27:37,100
merge companies work together to
kind of, you know, come up with 

481
00:27:37,100 --> 00:27:41,600
the strategy for this, this 
merger, so that end users don't.

482
00:27:41,700 --> 00:27:45,100
Don't get stuck in the land of 
total confusion. 

483
00:27:45,300 --> 00:27:47,400
But, you know, the other thing I
was thinking about is like, 

484
00:27:47,400 --> 00:27:50,900
imagine a scenario where two 
companies merge, they're both 

485
00:27:50,900 --> 00:27:55,900
using Office 365, they both are 
using in tune and they're 

486
00:27:55,900 --> 00:28:01,500
managing those end devices on in
tune with be it, you know, 

487
00:28:01,500 --> 00:28:04,600
laptops are more likely mobile 
phones. 

488
00:28:05,000 --> 00:28:10,400
Imagine that they also have, you
know, non-employee users in 

489
00:28:10,400 --> 00:28:14,600
their core directories Like 
Partners which to your point, 

490
00:28:14,800 --> 00:28:18,200
you could be leveraging the same
partner, so they might not be an

491
00:28:18,200 --> 00:28:20,900
employee user. 
Normally a person wouldn't be an

492
00:28:20,900 --> 00:28:24,700
employee of both organizations 
but certainly a third party 

493
00:28:24,700 --> 00:28:28,800
could have accounts on both 
sides and that could actually 

494
00:28:28,900 --> 00:28:34,900
absolutely be confusing but I 
think you know you have to with 

495
00:28:34,900 --> 00:28:37,800
all that complexity at all that 
you have to kind of dial it back

496
00:28:37,800 --> 00:28:41,600
into parts that you can control 
and try to isolate. 

497
00:28:41,700 --> 00:28:45,400
Eight the areas where you can 
merge where it makes sense and 

498
00:28:45,500 --> 00:28:47,900
try to minimize the impact 
Downstream. 

499
00:28:48,200 --> 00:28:51,600
And then, you know, you go after
some of these more complex Parts

500
00:28:51,900 --> 00:28:56,800
as late in the process as you 
can, I think it's probably a 

501
00:28:56,808 --> 00:28:58,900
good spot where we can pivot and
stop talking about all the 

502
00:28:58,908 --> 00:29:02,500
problems and maybe stuck start 
talking about. 

503
00:29:02,500 --> 00:29:05,500
So I things that are actually 
benefits right? 

504
00:29:05,500 --> 00:29:08,000
Or potential benefits, or 
opportunities, whatever way we 

505
00:29:08,000 --> 00:29:11,900
want to kind of spin it around. 
Okay, so we know we've got all 

506
00:29:11,900 --> 00:29:14,200
these issues. 
What are some of the positive 

507
00:29:14,200 --> 00:29:16,500
things that could come out of a 
merger? 

508
00:29:16,500 --> 00:29:19,100
Organs action acquisition from 
an identity for Sperry, right? 

509
00:29:19,100 --> 00:29:22,000
Yeah, I mean, that's that's 
great because I am an optimist, 

510
00:29:22,000 --> 00:29:25,900
believe it or not are like to 
think Of myself as an optimist. 

511
00:29:26,700 --> 00:29:31,000
You know what I think of you 
know say were the acquiring 

512
00:29:31,000 --> 00:29:35,300
company or the more senior 
organization in the merger 

513
00:29:35,700 --> 00:29:39,900
however you want to put that or 
even if your equals the idea 

514
00:29:39,900 --> 00:29:46,700
that the other company could 
have a better process, a better 

515
00:29:46,700 --> 00:29:49,700
mousetrap for some Mass 
effective. 

516
00:29:49,700 --> 00:29:55,200
I am so you've been on you know,
adfs for Forever. 

517
00:29:55,200 --> 00:29:57,700
Right? 
And you haven't been able to get

518
00:29:57,700 --> 00:30:01,800
the investment to move to a 
cloud base and say the company 

519
00:30:01,800 --> 00:30:06,000
that you're merging with has 
OCTA, that's not perfect 

520
00:30:06,000 --> 00:30:11,200
opportunity to you know, upgrade
your technical footprint and 

521
00:30:11,200 --> 00:30:15,300
hopefully you're all so you know
going to be bringing you on a 

522
00:30:15,308 --> 00:30:17,900
team of people who are expert in
that technology. 

523
00:30:17,900 --> 00:30:20,600
So that's a great opportunity 
right there. 

524
00:30:20,700 --> 00:30:23,200
What are your thoughts? 
Yeah, I think anytime that you 

525
00:30:23,200 --> 00:30:27,000
can grow from Expertise 
standpoint is great. 

526
00:30:27,100 --> 00:30:29,600
I think that's certainly in, on 
a win. 

527
00:30:30,500 --> 00:30:33,500
If you if you are able to get 
additional technologies, that 

528
00:30:33,500 --> 00:30:36,000
may be either you couldn't 
afford or just didn't get 

529
00:30:36,000 --> 00:30:38,800
approved or whatever, maybe from
from an acquisition. 

530
00:30:38,800 --> 00:30:42,200
I think that's great too. 
I think a lot of times companies

531
00:30:42,200 --> 00:30:46,400
who are doing acquiring tend to 
be more mature anyway, from a 

532
00:30:46,500 --> 00:30:48,600
information security and from 
add any perspective. 

533
00:30:48,600 --> 00:30:52,600
So there may be an opportunity 
to solve some Legacy challenges 

534
00:30:52,600 --> 00:30:55,200
that you might have had. 
If or being acquired, for 

535
00:30:55,200 --> 00:30:58,300
example and say, hey, okay well 
this company has you know, X 

536
00:30:58,300 --> 00:31:00,800
technology. 
We we didn't have that. 

537
00:31:00,800 --> 00:31:04,900
But now we do, how were we going
to take advantage of that sort 

538
00:31:04,900 --> 00:31:07,700
of thing to be able to, you 
know, deliver, better services 

539
00:31:07,700 --> 00:31:09,900
to the organization? 
You know, for my identity 

540
00:31:09,900 --> 00:31:12,100
standpoint, probably an 
opportunity to take advantage 

541
00:31:12,100 --> 00:31:16,700
of, you know, if there are, if 
there are better processes, it 

542
00:31:16,700 --> 00:31:20,400
can also be used as an excuse to
make it to make changes to the 

543
00:31:20,400 --> 00:31:22,000
environment. 
Say, okay, hey, you know what? 

544
00:31:22,200 --> 00:31:23,600
Well, we're going to those 
Acquisitions. 

545
00:31:23,600 --> 00:31:26,900
So because of that, That we're 
going to have to do X and 

546
00:31:26,900 --> 00:31:30,200
sometimes, you know, that that 
sort of kick in the pants is is 

547
00:31:30,200 --> 00:31:34,600
all you need to change mindsets 
or at least get the the momentum

548
00:31:34,600 --> 00:31:37,600
or the drive to maybe make 
things more standard or more 

549
00:31:37,600 --> 00:31:41,100
consistent through processes. 
So I think you can kind of get 

550
00:31:41,100 --> 00:31:43,700
creative sometimes around. 
You know how you want to kind of

551
00:31:43,700 --> 00:31:47,800
Leverage that change from at any
perspective and a merger or 

552
00:31:47,800 --> 00:31:52,600
exact acquisition or Eve or a 
divestiture is a seismic event 

553
00:31:52,600 --> 00:31:56,900
in the organization and it can 
certainly cover, you know, a lot

554
00:31:56,900 --> 00:32:00,000
of things that need to take 
place either from a people, a 

555
00:32:00,008 --> 00:32:01,700
process, or a technology 
standpoint. 

556
00:32:01,800 --> 00:32:05,500
The seismic event often comes 
with a special budget. 

557
00:32:05,900 --> 00:32:10,200
So there might be an opportunity
to invest in an area where you 

558
00:32:10,200 --> 00:32:13,800
have an invested before you even
take it to that very fundamental

559
00:32:13,800 --> 00:32:16,900
level. 
A lot of organizations, even 

560
00:32:16,900 --> 00:32:20,900
mature organizations, don't have
a mature. 

561
00:32:21,100 --> 00:32:26,000
I am program or I am strategy. 
so it might be an opportunity to

562
00:32:26,000 --> 00:32:29,000
reset around that, especially if
you've gone through an 

563
00:32:29,000 --> 00:32:32,300
acquisition and you can say, 
alright now let's do a 

564
00:32:32,300 --> 00:32:35,500
post-mortem on it and you start 
to say boy we could have 

565
00:32:35,500 --> 00:32:40,300
probably done this better had we
had a shot at she around how to 

566
00:32:40,300 --> 00:32:45,300
handle an acquisition or merger 
so movie we bring in some help 

567
00:32:45,300 --> 00:32:49,100
to help us plan around that and 
then to your point, you know, 

568
00:32:49,100 --> 00:32:54,000
usually even very mature 
organizations, have some areas 

569
00:32:54,000 --> 00:32:57,300
that Could be improved whether 
it's, you know, they can have a 

570
00:32:57,300 --> 00:33:01,200
better process or better 
technology for access management

571
00:33:01,200 --> 00:33:06,200
or something on the provisioning
and you know, role management 

572
00:33:06,200 --> 00:33:08,500
side or privileged access 
management side. 

573
00:33:08,700 --> 00:33:13,700
So the scope is large enough 
that you know, you can take take

574
00:33:14,100 --> 00:33:18,100
advantage of the opportunity to 
have an acquisition budget. 

575
00:33:18,100 --> 00:33:19,600
Potentially get some things 
done. 

576
00:33:19,700 --> 00:33:21,500
Yeah, for sure. 
I mean, don't overlook that 

577
00:33:21,500 --> 00:33:22,700
budget. 
I think we've seen it. 

578
00:33:23,300 --> 00:33:25,600
Yeah, the last few years is like
This thing called digital 

579
00:33:25,600 --> 00:33:27,700
transformation. 
And we've seen a lot of identity

580
00:33:27,700 --> 00:33:31,600
programs, sort of, get better, 
and sort of use. 

581
00:33:31,600 --> 00:33:34,500
Some of the funding, that might 
be available that to transform 

582
00:33:34,500 --> 00:33:36,700
the organization, whether it's 
like, internal Workforce or 

583
00:33:36,700 --> 00:33:38,300
maybe some sort of 
customer-facing thing. 

584
00:33:38,300 --> 00:33:41,800
But I think this is another 
another cover to get some, some 

585
00:33:41,800 --> 00:33:45,500
money into the. 
I am program that may be of use 

586
00:33:45,800 --> 00:33:47,700
and be able to kind of move 
things forward with that. 

587
00:33:48,700 --> 00:33:51,500
We've been hinting on sort of 
divestitures the whole time in. 

588
00:33:52,700 --> 00:33:55,000
I think probably now is a good 
time to kind of Think about that

589
00:33:55,000 --> 00:33:57,900
as well is what are some of the 
things from a divestiture 

590
00:33:57,900 --> 00:34:00,800
standpoint? 
Because for every, you know, I 

591
00:34:00,800 --> 00:34:03,000
feel like merger and acquisition
that's out there. 

592
00:34:03,000 --> 00:34:06,600
There is also the opposite that 
takes place where some part of 

593
00:34:06,600 --> 00:34:10,800
the organization or company is 
being spun out or wound down, or

594
00:34:10,800 --> 00:34:13,500
whatever it might look like. 
And there are certainly 

595
00:34:13,500 --> 00:34:15,900
challenges around that because 
those are not typically like a 

596
00:34:15,908 --> 00:34:19,300
normal run-of-the-mill 
separation or termination, 

597
00:34:19,300 --> 00:34:20,300
right. 
Those sort of thing. 

598
00:34:20,600 --> 00:34:22,100
What are some of the things that
you think about from a 

599
00:34:22,107 --> 00:34:25,199
divestiture standpoint before we
move on to Investors. 

600
00:34:25,199 --> 00:34:29,300
Can I bring up one other area? 
I guess around these challenges 

601
00:34:29,300 --> 00:34:33,900
and opportunities because they 
think these two are the two 

602
00:34:33,900 --> 00:34:37,000
things we're going to bring up 
our both potential challenges 

603
00:34:37,000 --> 00:34:40,199
and opportunities. 
So, the opportunities arise 

604
00:34:40,199 --> 00:34:43,699
around people. 
Potentially, you're acquiring a 

605
00:34:43,699 --> 00:34:49,100
company with talent and you can 
add that talent to your team. 

606
00:34:49,300 --> 00:34:52,000
The challenge is potentially 
those folks. 

607
00:34:52,000 --> 00:34:55,699
Don't realize that they're, you 
know, you're thinking about them

608
00:34:55,699 --> 00:34:58,900
in that way of, hey, there's 
there's going to be a new home 

609
00:34:58,900 --> 00:35:01,800
for me and I'm going to be 
happier than I was before. 

610
00:35:02,000 --> 00:35:05,400
So the challenge becomes You 
need to get in front of those 

611
00:35:05,400 --> 00:35:08,700
people and let them know that 
there's a place for them and 

612
00:35:08,700 --> 00:35:10,900
that you picture them in your 
future. 

613
00:35:11,300 --> 00:35:14,700
So people's one, the other I was
thinking of there's like so many

614
00:35:14,700 --> 00:35:21,900
more of our of clients that I 
interact with are moving to this

615
00:35:21,900 --> 00:35:27,500
manage operations, or MSP or 
mssp model where they've 

616
00:35:27,500 --> 00:35:30,200
outsourced. 
The day-to-day run activities of

617
00:35:30,200 --> 00:35:33,900
their info SEC and I am groups, 
maybe all of Mighty. 

618
00:35:34,300 --> 00:35:39,500
So, you're potentially in a 
merger scenario or acquisition 

619
00:35:39,500 --> 00:35:42,500
scenario, you've got two 
different msps. 

620
00:35:44,100 --> 00:35:47,700
Obviously, that could be a 
challenge like, you know, do you

621
00:35:47,800 --> 00:35:50,000
move forward with both of them 
in place? 

622
00:35:50,400 --> 00:35:53,300
Do you move forward and kick one
of them out? 

623
00:35:53,700 --> 00:35:56,100
You know, but it's also an 
opportunity right if one 

624
00:35:56,100 --> 00:35:59,700
organization has been unhappy 
with their managed service 

625
00:35:59,700 --> 00:36:01,900
provider. 
I mean, that's how I see that 

626
00:36:02,400 --> 00:36:04,900
you know, quite frankly Quite a 
lot. 

627
00:36:05,600 --> 00:36:10,000
So if one organization is very 
happy, the other organization is

628
00:36:10,200 --> 00:36:13,400
unhappy, I mean, there's a 
potential opportunity where 

629
00:36:14,200 --> 00:36:18,600
potentially lower your costs 
overall, for managing it and you

630
00:36:18,600 --> 00:36:22,100
could improve your service on at
least one of the one end of it. 

631
00:36:22,500 --> 00:36:26,000
You know, either the acquirer 
the acquiree, you know, going 

632
00:36:26,000 --> 00:36:28,900
back to real quick before you 
get back to dusters around 

633
00:36:28,900 --> 00:36:34,200
people and making sure people 
are under, you know, Part of the

634
00:36:34,207 --> 00:36:37,200
plan and understood but 
communicating that to the 

635
00:36:37,200 --> 00:36:41,500
employee is a very important 
part because it's certainly, you

636
00:36:41,500 --> 00:36:43,700
know, if you're thinking about 
is like, okay, well shoot, we're

637
00:36:43,700 --> 00:36:46,800
getting bought or we're selling 
something off, like what does it

638
00:36:46,800 --> 00:36:48,000
have to do with me? 
Right? 

639
00:36:48,000 --> 00:36:50,500
What am I going to? 
What does this mean for me, from

640
00:36:50,500 --> 00:36:53,900
a employment, standpoint this 
good or bad? 

641
00:36:54,400 --> 00:36:56,100
And the sooner you can share, 
you know? 

642
00:36:56,100 --> 00:36:59,500
News, hopefully it's good news. 
The better you will be off 

643
00:36:59,500 --> 00:37:04,100
because then, you know, people 
are aware of Of what's going on 

644
00:37:04,100 --> 00:37:05,900
where they're going to fit into 
the new organization or how 

645
00:37:05,900 --> 00:37:09,200
that's going to work, etc. 
You know, one of my mantras is 

646
00:37:09,200 --> 00:37:12,500
never wait to share good news 
with people because I've seen a 

647
00:37:12,508 --> 00:37:15,900
lot of times where, you know, 
that uncertainty, you know, 

648
00:37:15,900 --> 00:37:20,000
leads to something that you wish
hadn't hadn't happened, all 

649
00:37:20,000 --> 00:37:22,700
because you decided to wait, 
because you were trying to 

650
00:37:22,700 --> 00:37:26,200
coordinate something else or 
maybe share, good news, you know

651
00:37:26,200 --> 00:37:28,600
as soon as you can. 
I think that's a good mantra for

652
00:37:28,600 --> 00:37:29,400
me, at least. 
Yeah. 

653
00:37:29,400 --> 00:37:33,100
You and I were both recently 
involved with being in that. 

654
00:37:33,200 --> 00:37:36,200
Position, right? 
And I don't think when you say 

655
00:37:36,500 --> 00:37:38,800
people think we'll, how does 
this affect me? 

656
00:37:38,800 --> 00:37:42,400
There's nothing wrong with the 
person for thinking that, right?

657
00:37:42,400 --> 00:37:46,000
I mean that's, you know, any 
normalize what you should be 

658
00:37:46,000 --> 00:37:50,100
doing, it's normal. 
And so I think going into a 

659
00:37:50,100 --> 00:37:52,800
situation like that, if you're 
in management, you should be 

660
00:37:52,800 --> 00:37:56,800
thinking before going to be 
thinking that and get out ahead 

661
00:37:56,800 --> 00:37:57,600
of it. 
Yeah. 

662
00:37:57,700 --> 00:38:00,400
For the people that you really 
value their, you'd be really 

663
00:38:00,400 --> 00:38:02,600
disappointed. 
If you found out, they were 

664
00:38:02,600 --> 00:38:06,800
leaving You know, right around 
the time of the, you know, 

665
00:38:06,800 --> 00:38:09,600
acquisition taking place. 
Yeah, it's difficult time for 

666
00:38:09,600 --> 00:38:11,000
sure. 
So try to make sure if it's the 

667
00:38:11,000 --> 00:38:15,700
same page and again bring people
to especially the folks that are

668
00:38:15,707 --> 00:38:18,200
considered strategically 
organization is make sure 

669
00:38:18,200 --> 00:38:19,200
they're aware of what's going 
on. 

670
00:38:19,600 --> 00:38:21,700
Make sure they understand what 
their role will be and try to 

671
00:38:21,700 --> 00:38:25,900
share as much as you can. 
So, alright, let's get back to 

672
00:38:25,900 --> 00:38:29,200
divestitures. 
What are things to think about? 

673
00:38:29,200 --> 00:38:33,600
Because I think about this idea 
of like a carve-out, For 

674
00:38:33,607 --> 00:38:36,300
example, a lot of organizations 
are good at putting things 

675
00:38:36,300 --> 00:38:39,600
together, not necessarily good 
at breaking them apart and 

676
00:38:39,600 --> 00:38:41,500
that's one of things immediately
jumps to mind but I'm sure 

677
00:38:41,500 --> 00:38:42,600
you've got other thoughts on 
that. 

678
00:38:42,700 --> 00:38:44,100
You know, I think that you're 
right on. 

679
00:38:44,100 --> 00:38:48,300
So I've been a part of 
divestitures in the past and you

680
00:38:48,300 --> 00:38:53,600
know, typically what I saw was 
that when you divested company 

681
00:38:54,000 --> 00:38:59,500
included in that sale is some 
set of it systems and the folks 

682
00:38:59,700 --> 00:39:02,700
required to support those, it 
system. 

683
00:39:02,700 --> 00:39:06,300
So You know, it could be one of 
your networking people. 

684
00:39:06,300 --> 00:39:10,100
It could be you know one of your
I am people, but essentially 

685
00:39:10,100 --> 00:39:13,900
you're going to have to, you 
know, give that acquiring 

686
00:39:13,900 --> 00:39:16,800
company, the it systems to run 
the business, right? 

687
00:39:16,800 --> 00:39:19,200
They're not just buying the 
factory and none of the 

688
00:39:19,200 --> 00:39:21,800
computers and it systems that go
with it. 

689
00:39:21,800 --> 00:39:24,300
So the accounting system all 
that. 

690
00:39:24,400 --> 00:39:28,400
So you, you know, as much if 
you're in the business of, 

691
00:39:28,400 --> 00:39:30,700
you're going to divest a few 
companies. 

692
00:39:31,200 --> 00:39:34,100
Obviously, if you have that 
strategy and And as you're 

693
00:39:34,100 --> 00:39:37,700
developing systems, you can 
develop them in that way. 

694
00:39:37,700 --> 00:39:40,800
Each business maybe does have 
its own active directory domain.

695
00:39:40,800 --> 00:39:44,200
So then you just kind of break 
the trust and give them their 

696
00:39:44,200 --> 00:39:48,100
active directory and all goes 
well rather than having 

697
00:39:48,200 --> 00:39:53,000
everybody merged into, you know,
one OCTA instance, maybe you're 

698
00:39:53,000 --> 00:39:56,100
in a hub-and-spoke model and 
they get their spoke or the data

699
00:39:56,100 --> 00:40:00,200
is kind of already segmented. 
That is ideal. 

700
00:40:00,900 --> 00:40:02,500
One of the other things that 
came to mind. 

701
00:40:02,500 --> 00:40:05,800
There is just That you know, 
well, typically you're going to 

702
00:40:05,800 --> 00:40:08,500
have to divest some of your team
as well. 

703
00:40:08,500 --> 00:40:14,100
So, you know, if you're not 
completely decentralized, which 

704
00:40:14,100 --> 00:40:15,800
would be great, but usually not 
the case. 

705
00:40:15,800 --> 00:40:18,800
You're going to have to, you 
know, take some of your folks 

706
00:40:18,800 --> 00:40:23,500
from your corporate it and info 
SEC staff and give them over to 

707
00:40:23,500 --> 00:40:27,600
the new company. 
Those people may know shared 

708
00:40:27,600 --> 00:40:31,300
passwords and they may know, you
know, things that. 

709
00:40:31,300 --> 00:40:34,300
Well, at least let's just stick 
to Passwords for a second. 

710
00:40:34,300 --> 00:40:38,900
If somebody who shared passwords
service accounts or shared 

711
00:40:38,900 --> 00:40:43,100
passwords for routers and things
like that, those passwords need 

712
00:40:43,100 --> 00:40:46,500
to be changed. 
So I think, you know, step one 

713
00:40:46,800 --> 00:40:49,400
is trying to figure out anybody 
that your divest thing. 

714
00:40:49,800 --> 00:40:54,200
What are the passwords that they
know that you need to change? 

715
00:40:54,700 --> 00:40:57,300
It doesn't really sound that 
much different in that context 

716
00:40:57,300 --> 00:40:58,700
of like a normal separation, 
right? 

717
00:40:58,700 --> 00:41:02,100
Shouldn't you always be removing
access for people who have left 

718
00:41:02,100 --> 00:41:05,100
the organization or Road into a 
new, you know, position that 

719
00:41:05,100 --> 00:41:08,800
doesn't need access to things. 
I know we see the struggle of 

720
00:41:08,800 --> 00:41:11,500
time with a privileged access 
management especially shared 

721
00:41:11,500 --> 00:41:14,200
accounts rotating passwords. 
You know not everyone is 

722
00:41:14,200 --> 00:41:17,600
fortunate to have you know a 
tool that will automate automate

723
00:41:17,600 --> 00:41:21,300
that rotation of the secrets 
password Vault something of like

724
00:41:21,300 --> 00:41:24,400
privileged access agent tools 
like you know psychotic or the 

725
00:41:24,400 --> 00:41:27,500
Linea. 
Now Beyond trust cyber-ark, 

726
00:41:27,500 --> 00:41:30,000
those sorts of things and 
they're left sort of like in 

727
00:41:30,000 --> 00:41:33,100
this manual state where it's 
like okay well shoot Jim knew 

728
00:41:33,100 --> 00:41:35,800
all these Counts. 
I'm gonna have to go off and 

729
00:41:35,800 --> 00:41:38,900
change all these and hopefully 
we get them all. 

730
00:41:39,100 --> 00:41:42,200
It seems to be, you know, one of
the, one of the strategies I 

731
00:41:42,207 --> 00:41:44,800
know that you and I don't like 
building strategies based on 

732
00:41:44,800 --> 00:41:47,600
hope. 
So how do we, you know, validate

733
00:41:47,600 --> 00:41:51,000
that that stuff is taking place.
But you know even now with like 

734
00:41:51,100 --> 00:41:55,200
Cloud security, and the 
obfuscation sometimes of some of

735
00:41:55,207 --> 00:42:00,700
the identity permissions that go
with things like AWS gcp Azure 

736
00:42:00,900 --> 00:42:03,100
to lesser degrees of the 
measures a little little more 

737
00:42:03,100 --> 00:42:04,300
straightforward. 
For the adgroups. 

738
00:42:04,300 --> 00:42:09,100
But, you know, how are people 
getting access to some of these 

739
00:42:09,500 --> 00:42:11,800
Cloud infrastructure as a 
service or platforms, as a 

740
00:42:11,800 --> 00:42:14,400
service, whatever it may be 
understanding how the 

741
00:42:14,400 --> 00:42:17,000
permissions are working, how to 
counter for is a big part of it,

742
00:42:17,000 --> 00:42:19,100
too. 
Because we've certainly seen in 

743
00:42:19,100 --> 00:42:22,800
the mood, in the news. 
The last few few years of people

744
00:42:22,800 --> 00:42:26,900
having access to, for example, 
S3 buckets, that probably 

745
00:42:26,900 --> 00:42:30,500
shouldn't have had access to 
Beyond, you know, they're, 

746
00:42:30,500 --> 00:42:32,300
they're, they're stay with the 
organization. 

747
00:42:32,300 --> 00:42:34,500
It's no different for me. 
Least from a divestiture 

748
00:42:34,500 --> 00:42:39,500
standpoint was like, okay, it is
a termination and the goal is to

749
00:42:39,500 --> 00:42:44,300
make sure that the axis is 
removed in a timely manner to 

750
00:42:44,300 --> 00:42:47,300
whatever systems will not Remain
the challenge. 

751
00:42:47,400 --> 00:42:50,600
Is there, sometimes this 
transitive state where a person 

752
00:42:50,600 --> 00:42:54,700
might be in both roles, how do 
you make sure that access is 

753
00:42:54,700 --> 00:42:56,400
appropriate? 
And if there are things, we've 

754
00:42:56,400 --> 00:42:59,800
been carved out or separated. 
How do you make sure that the 

755
00:42:59,800 --> 00:43:02,700
right permissions, remove wrong,
permissions, go away. 

756
00:43:02,700 --> 00:43:05,900
You know, those sorts of Things.
So I think it's a complicated 

757
00:43:05,900 --> 00:43:10,100
scenario for sure, but if I try 
to keep it for my feeble brain, 

758
00:43:10,100 --> 00:43:12,300
as simple as I can, that makes 
it easier for me. 

759
00:43:12,400 --> 00:43:14,200
Yeah, well, takes a lot of 
planning. 

760
00:43:14,200 --> 00:43:19,700
It takes also having detective 
controls so that you can keep a 

761
00:43:19,707 --> 00:43:24,100
watch on what's Happening. 
I think what you mentioned there

762
00:43:24,100 --> 00:43:31,500
in terms of like all the the 
cloud reach Beyond kind of just 

763
00:43:31,500 --> 00:43:35,900
what's happening on your network
makes It harder to control, 

764
00:43:35,900 --> 00:43:39,400
makes it more complex, and I 
think that's why organizations 

765
00:43:39,400 --> 00:43:43,400
constantly find themselves 
falling behind is that the, the 

766
00:43:43,400 --> 00:43:47,300
world of it is changing so fast.
It's, you know, new services are

767
00:43:47,308 --> 00:43:51,900
coming online and it makes it 
harder to manage, then you throw

768
00:43:51,900 --> 00:43:57,600
a divestiture on top of it. 
So, yeah, again kind of the 

769
00:43:57,600 --> 00:44:04,100
divestiture and MMA stuff, 
really just has a You know, 

770
00:44:04,100 --> 00:44:07,800
Major Impact in terms of 
complexity challenges, but I 

771
00:44:07,800 --> 00:44:10,600
think on the on the flip side, 
it's opportunities as well. 

772
00:44:10,600 --> 00:44:15,100
And if you you know if you get 
it right potentially you can 

773
00:44:15,100 --> 00:44:18,600
grow your business exponentially
and that the acquisition like 

774
00:44:18,600 --> 00:44:21,300
we're talking about why the 
business is to the Acquisitions.

775
00:44:21,600 --> 00:44:25,000
It's because they believe that 
take this company, that's making

776
00:44:25,000 --> 00:44:28,500
a million dollars, a year, put 
it on our system and maybe it 

777
00:44:28,500 --> 00:44:31,700
can make ten million dollars a 
year because of the kindness of 

778
00:44:31,707 --> 00:44:34,000
their heart. 
The idea Is this? 

779
00:44:34,000 --> 00:44:36,200
Yeah, they don't want to make 
that examinees is to make more 

780
00:44:36,200 --> 00:44:39,400
money so it's just it's just the
way business is. 

781
00:44:39,400 --> 00:44:41,700
I think for my dining 
perspective is kind of start to 

782
00:44:41,700 --> 00:44:45,200
wrap things up, is try to keep 
it simple as much as you can. 

783
00:44:45,200 --> 00:44:50,000
These are complex situations, 
but if you try to break it down 

784
00:44:50,000 --> 00:44:53,600
from an identity perspective, 
we're still talking the same 

785
00:44:53,600 --> 00:44:57,500
Concepts who has access to what 
and is that appropriate. 

786
00:44:58,200 --> 00:45:02,300
So boarding off-boarding the 
changes, those are still the 

787
00:45:02,300 --> 00:45:05,100
same type of life cycle. 
Well, events that are probably 

788
00:45:05,100 --> 00:45:08,100
taking place, you know, 
throughout the challenge here is

789
00:45:08,100 --> 00:45:12,600
that it's a new organization, 
they may or may not have a easy 

790
00:45:12,600 --> 00:45:16,500
path in and there may be some 
options that need to be 

791
00:45:16,500 --> 00:45:20,100
triggered to be able to support 
sort of that that move over or 

792
00:45:20,100 --> 00:45:21,800
move out whatever that looks 
like. 

793
00:45:21,800 --> 00:45:25,800
So again I try to keep things as
simple as possible and try to, 

794
00:45:25,800 --> 00:45:28,800
you know, the life and the world
was already complex. 

795
00:45:28,800 --> 00:45:31,600
We don't try to make it complex,
even more complex. 

796
00:45:31,600 --> 00:45:34,800
Just just for know, A reason 
doesn't make any sense to me. 

797
00:45:34,800 --> 00:45:37,200
So, again, try to keep it simple
as kind of a things and, 

798
00:45:37,400 --> 00:45:40,600
hopefully, that that makes makes
things go smoother As you move 

799
00:45:40,600 --> 00:45:43,200
through this process. 
Yeah, that's great advice. 

800
00:45:43,400 --> 00:45:46,100
All right, so we should start to
wrap things up, but you and I 

801
00:45:46,100 --> 00:45:48,700
have been on the road. 
I've been on the road for two 

802
00:45:48,700 --> 00:45:50,600
straight weeks, which is great 
times. 

803
00:45:51,700 --> 00:45:53,200
And you've been on the road I 
think for the first time in a 

804
00:45:53,207 --> 00:45:58,600
while for all week with, you 
know with me I got me and you 

805
00:45:58,600 --> 00:46:02,200
thinking about some of the trips
that we've taken in the past and

806
00:46:02,200 --> 00:46:04,200
you had a good one that I 
thought would We'd bring to cut 

807
00:46:04,200 --> 00:46:06,700
kind of white here. 
Is what was your first 

808
00:46:06,700 --> 00:46:10,300
international business trip and 
you could stories around it. 

809
00:46:10,500 --> 00:46:12,700
Yeah, good sir. 
And and the reason we picked 

810
00:46:12,700 --> 00:46:17,700
International talk about is that
I did have a first domestic trip

811
00:46:17,700 --> 00:46:21,600
but it was pretty uneventful. 
My first international trip was 

812
00:46:21,800 --> 00:46:27,100
to Frankfurt, Germany. 
And on, during the landing, 

813
00:46:27,500 --> 00:46:31,600
there is a little kid sitting in
the row behind me, and he 

814
00:46:31,600 --> 00:46:35,700
started crying and Not sure why 
I was crying but then I found 

815
00:46:35,700 --> 00:46:40,700
out pretty quickly because he 
vomited over the seat on the guy

816
00:46:40,700 --> 00:46:43,200
next to me and there's splashed 
on me. 

817
00:46:43,800 --> 00:46:48,300
So, I mean gross before I was 
pretty fortunate that I wasn't 

818
00:46:48,300 --> 00:46:51,900
like I didn't bear the brunt of 
it but the guy next to me got 

819
00:46:52,200 --> 00:46:55,700
God blasted. 
And I mean even if you get one 

820
00:46:55,700 --> 00:46:59,900
drop of vomit on you, it's 
really bad. 

821
00:47:00,000 --> 00:47:03,300
Now I heard the appropriate 
number of drops is 0. 

822
00:47:03,400 --> 00:47:06,100
In case you're wondering. 
Yes. 

823
00:47:06,400 --> 00:47:11,200
Yeah if you're doing if you're 
playing at home but yeah it was 

824
00:47:11,200 --> 00:47:13,200
pretty bad. 
Someone had mentioned to me 

825
00:47:13,200 --> 00:47:20,700
early in my travel days like try
to be as empathetic to the 

826
00:47:20,700 --> 00:47:23,300
people around you as possible 
and traveling because nobody's 

827
00:47:23,300 --> 00:47:26,900
having your time and you know 
like I didn't take this as an 

828
00:47:26,900 --> 00:47:29,900
opportunity to blow up. 
Now, the guy next to me was 

829
00:47:29,900 --> 00:47:34,200
furious and I think probably if 
I get blessed with Like you did.

830
00:47:34,200 --> 00:47:37,300
I probably would have been 
Furious too but I tried to take 

831
00:47:37,300 --> 00:47:38,700
it in stride as much as 
possible. 

832
00:47:38,700 --> 00:47:42,300
The mother whose with the kid 
was almost in tears. 

833
00:47:42,300 --> 00:47:44,500
I mean, she felt horrible about 
it. 

834
00:47:45,300 --> 00:47:47,400
But I mean that was my very 
first trip. 

835
00:47:47,400 --> 00:47:51,400
So lend in Germany got vomited 
on, went directly to the 

836
00:47:51,400 --> 00:47:54,800
bathroom. 
Took off my shirt wash, it 

837
00:47:54,800 --> 00:47:58,000
didn't put it back on and put 
something else on. 

838
00:47:58,000 --> 00:48:00,600
But yeah, I'll never forget that
one. 

839
00:48:01,100 --> 00:48:03,200
How about you? 
Yeah, I'll bet that's it. 

840
00:48:03,200 --> 00:48:05,700
That's It's a not a great way to
start. 

841
00:48:05,700 --> 00:48:08,200
I guess, I guess that's one way 
to stamp a passport. 

842
00:48:08,900 --> 00:48:11,400
I would just rather ink instead.
Yeah, yeah. 

843
00:48:11,400 --> 00:48:16,800
And you know, it wasn't, it 
wasn't a bad trip but I had not 

844
00:48:16,800 --> 00:48:20,700
dealt with that kind of jet lag 
before. 

845
00:48:20,700 --> 00:48:24,800
So, six hours difference and I'd
be laying there at night, after 

846
00:48:24,800 --> 00:48:28,000
working all day, and being 
exhausted and just staring at 

847
00:48:28,000 --> 00:48:31,100
the ceiling because I my body 
wouldn't adjust. 

848
00:48:31,100 --> 00:48:34,400
And then when I got home and 
there's only six hours, But you 

849
00:48:34,400 --> 00:48:38,200
know is my first first time 
experiencing that it was the 

850
00:48:38,207 --> 00:48:41,000
same way. 
I think my first trip was to 

851
00:48:41,000 --> 00:48:45,300
India going from Chicago to 
India, which was a nineteen and 

852
00:48:45,300 --> 00:48:48,000
a half hour. 
I think total travel time 

853
00:48:48,000 --> 00:48:53,200
between airports to get there. 
I had a good trip. 

854
00:48:53,200 --> 00:48:57,100
I mean, as far as, you know, 
experiences go is my first 

855
00:48:57,100 --> 00:49:03,000
international business trip, you
know, it was a long trip, that's

856
00:49:03,000 --> 00:49:03,500
for sure. 
Sure. 

857
00:49:03,500 --> 00:49:06,800
But the actual experience was 
great and you know was there on 

858
00:49:06,800 --> 00:49:10,400
business with the partner that 
we were working with and going 

859
00:49:10,400 --> 00:49:14,600
through a scenario that we had 
just talked about and, you know,

860
00:49:14,700 --> 00:49:17,900
the, the experience was great. 
I got a chance to sort of open 

861
00:49:17,900 --> 00:49:22,500
my eyes to other cultures and 
kind of see how other folks 

862
00:49:22,500 --> 00:49:25,800
around the world lived. 
And I think that was, you know, 

863
00:49:25,800 --> 00:49:28,700
a sign of an Awakening moment, 
you know, having lived in my 

864
00:49:28,700 --> 00:49:31,400
bubble in the Chicago area for a
number of years. 

865
00:49:31,400 --> 00:49:35,200
At that point, not really having
that exposure You know, shout 

866
00:49:35,200 --> 00:49:39,800
out to the folks that I was with
making sure that spicy food was 

867
00:49:39,800 --> 00:49:43,500
kept to a minimum protecting me 
from hopefully making any too 

868
00:49:43,500 --> 00:49:48,000
many stupid American mistakes in
a foreign country but just being

869
00:49:48,000 --> 00:49:51,100
able to kite, go meet the other 
folks you know, I got to see 

870
00:49:51,100 --> 00:49:55,600
mahabalipuram and the shore 
Temple and a bunch of stuff in 

871
00:49:55,600 --> 00:49:59,200
the Chennai area of India. 
It was very hot which as you 

872
00:49:59,200 --> 00:50:04,100
know is My Kryptonite hot and 
humid not A great combination 

873
00:50:04,100 --> 00:50:07,800
for me but the actual trip 
itself was so positive. 

874
00:50:08,500 --> 00:50:10,900
It was, it was a good experience
for me, certainly long from a 

875
00:50:10,900 --> 00:50:16,100
travel perspective but I'm glad 
I went and certainly was a good 

876
00:50:16,100 --> 00:50:18,500
experience. 
Like I said and you get vomited 

877
00:50:18,500 --> 00:50:20,200
on. 
No, I def, I did not. 

878
00:50:20,200 --> 00:50:22,600
It was a, it was a, it was a 
good trip. 

879
00:50:22,600 --> 00:50:25,900
No, no vomit vomit. 
Free trip. 

880
00:50:25,900 --> 00:50:27,200
Wow. 
This is so weird. 

881
00:50:27,300 --> 00:50:31,100
So unusual, right? 
Yeah, I hopefully that's a no. 

882
00:50:31,100 --> 00:50:32,800
I mean, hopefully that's the uh,
normal. 

883
00:50:33,400 --> 00:50:36,200
Strictest, you're not gonna say 
it. 

884
00:50:36,200 --> 00:50:38,900
Only happened to me once it just
happens to be my first trip. 

885
00:50:38,900 --> 00:50:41,100
It was a scarring incident. 
What can you say? 

886
00:50:41,600 --> 00:50:42,800
You can. 
All right, let's go ahead and 

887
00:50:42,800 --> 00:50:45,000
wrap up because we were starting
to ramble a little bit. 

888
00:50:45,200 --> 00:50:47,900
It is definitely a Saturday. 
I got to turn this around to a 

889
00:50:47,900 --> 00:50:51,000
show for Monday, so we'll go 
ahead and leave it there, you 

890
00:50:51,008 --> 00:50:54,200
know, I think, you know, as we 
kind of think about this Ma and 

891
00:50:54,200 --> 00:50:57,400
identity perspective and we 
talked, I feel like we spent 

892
00:50:57,400 --> 00:50:59,600
more time on sort of like the 
challenges. 

893
00:51:00,600 --> 00:51:03,400
But as I'm sitting here thinking
about the conversation, a lot of

894
00:51:03,400 --> 00:51:06,200
the challenges are things that 
you're probably already dealing 

895
00:51:06,200 --> 00:51:09,200
with already. 
It's just not in the context, 

896
00:51:09,200 --> 00:51:12,700
maybe of a merger or an 
acquisition or a divestiture, 

897
00:51:13,300 --> 00:51:15,500
but it's still again that same 
concept of onboarding 

898
00:51:15,500 --> 00:51:19,300
off-boarding changes right to 
Identity, the system's being 

899
00:51:19,300 --> 00:51:21,400
available, right? 
How are they going to be 

900
00:51:21,400 --> 00:51:24,900
utilized with any memorization? 
So, hopefully, hopefully this 

901
00:51:24,900 --> 00:51:27,400
conversation made sense and if 
you've got comments around it, 

902
00:51:27,400 --> 00:51:28,900
you know, certainly paying us on
LinkedIn. 

903
00:51:28,900 --> 00:51:31,400
We're happy to Tell it tell us, 
we're crazy. 

904
00:51:31,400 --> 00:51:33,400
Tell us like, yeah, you know War
stories about it. 

905
00:51:33,400 --> 00:51:35,700
We're always happy about that 
maybe even better maybe. 

906
00:51:35,700 --> 00:51:38,100
Come on the show and kind of 
talk through some of the 

907
00:51:38,100 --> 00:51:39,700
challenges. 
Maybe you face in the real world

908
00:51:39,700 --> 00:51:42,300
wrong with HEPA to have folks in
the real world come on. 

909
00:51:42,300 --> 00:51:45,100
But any final thoughts before we
close it up for this week? 

910
00:51:45,100 --> 00:51:46,300
Jim. 
Yeah. 

911
00:51:46,300 --> 00:51:50,200
Just thinking exactly what you 
said about the, you know, adding

912
00:51:50,200 --> 00:51:53,700
your comment to LinkedIn. 
Every Monday noon eastern time 

913
00:51:53,700 --> 00:51:57,800
in the u.s. 
Jeff post a post on LinkedIn to 

914
00:51:57,800 --> 00:52:00,100
let everyone knows that the 
episodes out. 

915
00:52:00,300 --> 00:52:05,000
Out adding a comment there would
certainly be welcome and then of

916
00:52:05,000 --> 00:52:08,700
course feel free to direct 
message us on LinkedIn 

917
00:52:08,700 --> 00:52:11,500
especially if you're going to 
Gartner and we have that 

918
00:52:11,500 --> 00:52:16,200
opportunity to to meet. 
We'd love to interact in person.

919
00:52:16,600 --> 00:52:18,400
Yeah, definitely. 
If you're going to Gartner, we 

920
00:52:18,400 --> 00:52:19,900
will be there. 
We hope to see folks there as 

921
00:52:19,900 --> 00:52:23,600
well. 
We put on our golden podcast 

922
00:52:23,600 --> 00:52:26,500
pants just like everyone else. 
We'd be happy to do fist bumps, 

923
00:52:26,800 --> 00:52:28,700
you know, if you want to watch a
show getting recorded, you know,

924
00:52:28,700 --> 00:52:31,200
that's, that's certainly an 
option or beyond the No, hit us 

925
00:52:31,200 --> 00:52:33,400
up on LinkedIn. 
We're happy to accommodate that 

926
00:52:33,400 --> 00:52:36,400
as best as we can. 
So all right with that, we'll go

927
00:52:36,400 --> 00:52:37,900
ahead and leave it there for 
this week. 

928
00:52:38,000 --> 00:52:40,400
We're on the web. 
I'd any at the center.com we're 

929
00:52:40,400 --> 00:52:45,800
on Twitter at idac podcast and 
we've enjoyed this conversation 

930
00:52:45,800 --> 00:52:49,300
and hopefully you did as well 
and we'll talk with everyone in 

931
00:52:49,300 --> 00:52:55,100
the next. 
Thanks for listening to the 

932
00:52:55,100 --> 00:52:57,900
identity at the center podcast. 
If you like what you heard, 

933
00:52:57,900 --> 00:53:01,200
don't forget to subscribe and 
visit us on the web and identity

934
00:53:01,200 --> 00:53:02,400
at the center.com.