WEBVTT

NOTE
This file was generated by Descript 

00:00:01.830 --> 00:00:05.310
Speaker: Simply Defensive brings you
the industry's top practitioners,

00:00:05.400 --> 00:00:12.870
innovators, and leaders to inform,
educate, and join us defensive.

00:00:25.448 --> 00:00:28.568
Josh Mason:  Hello and welcome to the
latest episode of Simply Defensive.

00:00:28.628 --> 00:00:31.418
Uh, I'm Josh Mason, as always.

00:00:31.418 --> 00:00:34.028
I've got my good friend, Wade Wells here.

00:00:35.528 --> 00:00:36.518
What's up?

00:00:36.668 --> 00:00:41.018
Happy whatever time it is that you're
listening to this podcast 'cause

00:00:41.018 --> 00:00:42.908
we're recording super into the future.

00:00:43.358 --> 00:00:43.748
Yep.

00:00:44.318 --> 00:00:48.518
And, uh, today we've got with
us one of our good friends from

00:00:48.518 --> 00:00:50.678
Black Hills Information Security.

00:00:50.708 --> 00:00:51.398
Uh, Tom.

00:00:51.968 --> 00:00:53.858
Tom, welcome to Simply Defensive.

00:00:56.093 --> 00:00:56.753
Tom Dejong: Hey, thanks.

00:00:56.753 --> 00:00:57.838
Happy to be here with you guys.

00:00:59.768 --> 00:01:01.238
Josh Mason: uh, tell people
a little bit yourself.

00:01:01.268 --> 00:01:06.548
I know you work at the soc there
and, uh, we've had Hayden on and

00:01:06.578 --> 00:01:08.618
you all work together as well.

00:01:09.128 --> 00:01:11.003
But yeah, introduce
yourself to the people.

00:01:13.898 --> 00:01:14.168
Tom Dejong: Yep.

00:01:14.198 --> 00:01:14.648
So,

00:01:14.648 --> 00:01:17.138
uh, I work in the BHIS SOC here.

00:01:17.198 --> 00:01:21.038
Uh, I'm, well, I'm the triage
lead, so mainly working tickets.

00:01:21.098 --> 00:01:26.288
Uh, I have got pulled into some
IR engagements in the past.

00:01:26.318 --> 00:01:27.818
Um, and let's see here.

00:01:27.818 --> 00:01:31.358
I run some tabletop exercises
for some of the clients if they,

00:01:31.388 --> 00:01:32.978
uh, contract that out from us.

00:01:33.038 --> 00:01:36.758
And I'm also the mentor to
the new hires and interns.

00:01:37.703 --> 00:01:39.848
Josh Mason: Nice, so.

00:01:40.628 --> 00:01:44.678
You or how you've only been with
Black Hills for a couple years now.

00:01:44.768 --> 00:01:49.058
Um, is it, how did you
get into cybersecurity?

00:01:52.118 --> 00:01:52.358
Tom Dejong: Yep.

00:01:52.388 --> 00:01:52.898
So I would've

00:01:52.958 --> 00:01:53.108
Josh Mason: Yeah,

00:01:53.228 --> 00:01:53.378
Tom Dejong: with

00:01:53.433 --> 00:01:53.723
Josh Mason: nice.

00:01:54.608 --> 00:01:58.508
Tom Dejong: I originally came on
as an intern, so, so how I got into

00:01:58.508 --> 00:02:01.058
cybersecurity, um, let's see here.

00:02:01.058 --> 00:02:04.028
Well, so South Dakota has this cool thing.

00:02:04.028 --> 00:02:05.918
It's called the Build Dakota Scholarship.

00:02:06.008 --> 00:02:09.098
Uh, so, so basically it kind of
works like an apprenticeship.

00:02:09.458 --> 00:02:13.598
Uh, so you'll get a full ride
through an in demand trade.

00:02:13.598 --> 00:02:17.078
So there would be like, it was
one of 'em, or, you know, uh.

00:02:17.453 --> 00:02:18.623
HVAC electrician.

00:02:19.373 --> 00:02:22.013
anyway, they'll give you a full
ride scholarship and then you work

00:02:22.013 --> 00:02:23.543
in the state for three years after.

00:02:24.023 --> 00:02:28.613
Uh, so I was just looking, uh, you
know, I was about 26 and thinking, uh, I

00:02:28.613 --> 00:02:32.033
probably better figure out a career, and
it sounded like it would be the easiest

00:02:32.033 --> 00:02:34.163
on my, uh, on my body in the long run.

00:02:34.163 --> 00:02:36.143
So, so I ended up going through that.

00:02:36.183 --> 00:02:40.053
And, uh, actually really
ended up enjoying computers.

00:02:40.113 --> 00:02:43.953
Um, so I thought it was super
interesting and I was always gravitated

00:02:43.953 --> 00:02:47.103
towards the cybersecurity, uh, topics.

00:02:47.103 --> 00:02:48.723
And it was funny.

00:02:48.723 --> 00:02:53.673
I was trying to, uh, was, I'd get so
frustrated about like not understanding

00:02:53.673 --> 00:02:58.143
what DNS was or something like
that, uh, when I was starting out.

00:02:58.143 --> 00:03:00.693
So I would listen to
Dark Net Diaries a lot.

00:03:00.703 --> 00:03:02.413
And just podcasts in general.

00:03:02.413 --> 00:03:06.733
But Darknet Diary specifically, I was
listening to it one morning, uh, while

00:03:06.733 --> 00:03:10.903
I was getting ready to go to school,
and it was an episode with John Strand.

00:03:11.293 --> 00:03:15.373
I heard him talking and saying, oh
yeah, I'm from Spearfish, South Dakota.

00:03:15.778 --> 00:03:17.758
And in my mind I was like, no way.

00:03:17.883 --> 00:03:20.038
I'm, I'm in Spearfish,
South Dakota right now.

00:03:20.038 --> 00:03:20.818
This is crazy.

00:03:21.238 --> 00:03:25.888
So, so anyway, I ended up going to,
uh, the, the teacher and talking about

00:03:25.888 --> 00:03:28.018
maybe doing the internship with them.

00:03:28.018 --> 00:03:31.468
And, uh, I think at that time
I didn't know if the SOC was

00:03:31.468 --> 00:03:32.758
fully established back then.

00:03:32.758 --> 00:03:35.488
So, uh, you know, they kind of
wanted to have more programming

00:03:35.488 --> 00:03:37.018
experience for the testers.

00:03:37.408 --> 00:03:40.798
Uh, but, but then in the second year, uh.

00:03:41.888 --> 00:03:44.858
I ended up getting an opportunity
and, uh, my first day was at

00:03:44.858 --> 00:03:47.168
Wild West Hacking Fest in 2022,

00:03:48.413 --> 00:03:49.043
Josh Mason: Nice.

00:03:49.208 --> 00:03:50.378
Tom Dejong: how I kind of got into it.

00:03:51.698 --> 00:03:52.358
Josh Mason: That's a,

00:03:52.968 --> 00:03:58.583
Wade Wells: I think it was established
by then, but it was like crew.

00:03:59.063 --> 00:04:01.763
I'm trying to remember all
the people who worked it like.

00:04:02.408 --> 00:04:05.078
I remember some names, but I don't
wanna like put 'em on blast or anything,

00:04:05.193 --> 00:04:05.413
Tom Dejong: Yep.

00:04:05.418 --> 00:04:05.468
Yep.

00:04:05.888 --> 00:04:07.868
Wade Wells: because that, I don't
think they work there anymore.

00:04:08.288 --> 00:04:09.428
Josh Mason: we got a lot
of good friends there.

00:04:09.443 --> 00:04:10.138
Tom Dejong: who you're talking about.

00:04:10.808 --> 00:04:11.108
Wade Wells: Yeah.

00:04:12.518 --> 00:04:12.978
Tom Dejong: Oh yeah.

00:04:14.438 --> 00:04:15.128
Josh Mason: That's awesome.

00:04:15.308 --> 00:04:15.638
Uh.

00:04:16.958 --> 00:04:18.608
So you started working at the soc.

00:04:18.668 --> 00:04:20.318
Um, you've learned quite a bit.

00:04:20.318 --> 00:04:24.398
You've been to a few Wild West
Fest because they're deadwood's

00:04:24.398 --> 00:04:25.448
right in your backyard.

00:04:25.778 --> 00:04:33.848
Um, you just did a workshop this last
week, uh, when we're filming this.

00:04:34.238 --> 00:04:36.368
Uh, how was that?

00:04:37.328 --> 00:04:37.838
Kind of

00:04:39.158 --> 00:04:39.548
Tom Dejong: So

00:04:39.548 --> 00:04:39.788
Josh Mason: lot.

00:04:40.143 --> 00:04:40.363
Wade Wells: So.

00:04:40.688 --> 00:04:42.548
Tom Dejong: I, I guess
it was just a webcast.

00:04:42.548 --> 00:04:45.278
I don't know if I'd say it was
the full workshop or not, but

00:04:45.308 --> 00:04:45.758
Josh Mason: Yeah.

00:04:46.118 --> 00:04:48.008
Tom Dejong: Uh, yeah, we just,
that just aired yesterday.

00:04:48.008 --> 00:04:51.728
So, uh, it was about how
to triage alerts coming in.

00:04:52.148 --> 00:04:53.138
Uh, I feel like.

00:04:53.868 --> 00:04:57.543
The, the sock topics that
BHIS gets are in high demand.

00:04:57.543 --> 00:05:00.843
So, uh, it's always fun to get to
put 'em out there and get, to get

00:05:00.843 --> 00:05:02.193
to see what the community likes.

00:05:02.193 --> 00:05:05.643
But, but yeah, it was, uh, I
definitely put a lot of work into it.

00:05:05.643 --> 00:05:10.023
So it can be tough to do those
webcast while you're to also work

00:05:10.023 --> 00:05:11.403
sock tickets in the background.

00:05:11.403 --> 00:05:13.083
But I feel like it pays off.

00:05:13.088 --> 00:05:16.923
I, I love hearing back from the community
about, uh, how it helped them or, you

00:05:16.923 --> 00:05:18.753
know, even if it can help one person.

00:05:19.053 --> 00:05:20.253
Uh, I'm happy with that.

00:05:20.873 --> 00:05:21.953
Josh Mason: Yeah, it

00:05:22.143 --> 00:05:22.708
Wade Wells: Yeah, I watched it.

00:05:22.863 --> 00:05:23.283
it was good.

00:05:23.313 --> 00:05:24.873
You had great points, right?

00:05:24.933 --> 00:05:27.663
You're going back and forth
on all the different things.

00:05:28.023 --> 00:05:28.563
uh.

00:05:28.773 --> 00:05:31.153
hit me right at home from
what I used do all day too.

00:05:31.153 --> 00:05:31.163
So.

00:05:31.208 --> 00:05:33.338
Tom Dejong: I may be having
some technical issues on my end.

00:05:33.338 --> 00:05:35.378
I can't hear anything right now.

00:05:35.678 --> 00:05:36.068
Josh Mason: Okay.

00:05:36.158 --> 00:05:37.088
Wade Wells: Uh, oh.

00:05:37.928 --> 00:05:39.638
Josh Mason: check your headset.

00:05:41.018 --> 00:05:42.848
I guess you can't hear me, so,

00:05:43.358 --> 00:05:44.108
Wade Wells: He's, he is wearing

00:05:44.493 --> 00:05:45.023
Josh Mason: yeah, right.

00:05:48.193 --> 00:05:51.493
Um, is it like your, your headset.

00:05:56.723 --> 00:05:56.963
Yeah.

00:05:56.963 --> 00:05:57.203
Right.

00:05:57.263 --> 00:05:57.863
We can text him.

00:05:58.028 --> 00:05:58.148
Tom Dejong: Hmm.

00:06:03.258 --> 00:06:04.373
What is happening?

00:06:05.213 --> 00:06:06.203
Can you guys still hear me?

00:06:07.583 --> 00:06:07.793
Okay?

00:06:08.753 --> 00:06:09.173
Josh Mason: Yeah,

00:06:09.448 --> 00:06:10.283
Tom Dejong: What is going on?

00:06:14.428 --> 00:06:14.648
Oh,

00:06:15.713 --> 00:06:16.403
Josh Mason: it happens.

00:06:17.603 --> 00:06:17.933
Um.

00:06:18.053 --> 00:06:18.293
Tom Dejong: yep.

00:06:18.293 --> 00:06:18.443
I,

00:06:18.503 --> 00:06:19.613
Josh Mason: I'll say things

00:06:19.853 --> 00:06:19.973
Tom Dejong: what

00:06:20.123 --> 00:06:22.073
Josh Mason: the off chance
that you can hear me.

00:06:22.853 --> 00:06:23.723
Can you hear me now?

00:06:25.733 --> 00:06:26.213
Okay.

00:06:26.348 --> 00:06:26.428
Wade Wells: right.

00:06:26.993 --> 00:06:27.623
Josh Mason: That's okay.

00:06:29.903 --> 00:06:31.883
Uh, Wade, you were asking,

00:06:34.253 --> 00:06:34.553
Wade Wells: No,

00:06:34.583 --> 00:06:35.368
Josh Mason: oh, you were talking about

00:06:35.393 --> 00:06:37.193
Wade Wells: it was more of a comment
you can keep you, you can go ask.

00:06:37.403 --> 00:06:37.583
Yeah.

00:06:37.763 --> 00:06:38.693
Josh Mason: the webinar?

00:06:38.843 --> 00:06:39.323
Um,

00:06:39.383 --> 00:06:40.493
Wade Wells: watched the webcast.

00:06:40.493 --> 00:06:40.793
yeah.

00:06:40.823 --> 00:06:41.063
Yeah.

00:06:41.063 --> 00:06:41.633
It was good.

00:06:41.633 --> 00:06:44.963
So it was a webcast because the,
the workshops are like four hours

00:06:44.963 --> 00:06:46.943
long, which are a lot of work.

00:06:47.058 --> 00:06:47.958
Tom Dejong: Yep, I get that.

00:06:48.083 --> 00:06:50.273
Wade Wells: asked me to do one
recently, and I'm like, uh, I

00:06:50.273 --> 00:06:51.113
don't know if I wanna do one.

00:06:53.363 --> 00:06:53.938
Uh, but no.

00:06:55.028 --> 00:06:55.958
All your points are good.

00:06:55.958 --> 00:06:58.508
Like, like right, the, the
initial investigation on the

00:06:58.508 --> 00:06:59.738
who, what, where, when, and why.

00:06:59.798 --> 00:07:00.278
Right?

00:07:00.488 --> 00:07:03.548
And knowing what to pivot off
of is half the battle, right?

00:07:03.878 --> 00:07:06.548
Looking at a log and understanding
like, okay, an IP address

00:07:06.548 --> 00:07:07.628
is something I can pivot.

00:07:07.658 --> 00:07:12.608
A hash, a process name, whether it
be a network connection, or even

00:07:12.608 --> 00:07:14.348
where the process location is, right?

00:07:14.528 --> 00:07:15.128
All of that.

00:07:15.128 --> 00:07:19.478
is something to then verify if that's
normal or not, and then keep moving and

00:07:19.718 --> 00:07:21.128
Tom Dejong: I appreciate the kind words.

00:07:21.368 --> 00:07:21.968
Wade Wells: to show that it's

00:07:22.298 --> 00:07:23.648
Tom Dejong: I'm glad that
it turned out all right.

00:07:23.828 --> 00:07:24.998
Wade Wells: or a false positive, so.

00:07:25.658 --> 00:07:29.978
Tom Dejong: yeah, it can be hard
to do these soc webcasts because so

00:07:29.978 --> 00:07:33.158
many of the things are, you know, it
varies so much and it can be such a

00:07:33.158 --> 00:07:36.368
variable thing, um, that it's kind
of hard to cover all the bases.

00:07:36.368 --> 00:07:38.983
Like I, I'm in the, in that one
section, it was just like, well.

00:07:39.643 --> 00:07:42.223
I mean, all this stuff is
kind of geared towards process

00:07:42.223 --> 00:07:44.113
execution and stuff like that.

00:07:44.113 --> 00:07:47.983
I tried to cover my bases a little bit,
but uh, you know, it can, there's just

00:07:47.983 --> 00:07:51.703
so much, so many different log sources
you're doing, and it, it can be a lot.

00:07:59.693 --> 00:08:00.053
Wade Wells: Oh yeah.

00:08:00.158 --> 00:08:00.278
Tom Dejong: I.

00:08:00.413 --> 00:08:01.073
Wade Wells: definitely.

00:08:01.933 --> 00:08:06.008
Josh Mason: Yeah, it's, uh, impressive
being able to pull it all together for

00:08:06.543 --> 00:08:08.558
a, a, a presentation like that though.

00:08:09.008 --> 00:08:11.558
Um, is this, was it your first

00:08:11.708 --> 00:08:12.758
Tom Dejong: done a conference talk

00:08:12.788 --> 00:08:14.408
Josh Mason: or have you
done conference talks?

00:08:14.708 --> 00:08:18.038
Tom Dejong: uh, for BHIS and
that was about, uh, how to

00:08:18.038 --> 00:08:19.418
do an email investigation.

00:08:19.418 --> 00:08:21.038
So, so this was the second one?

00:08:21.098 --> 00:08:25.388
Um, I got asked to do the Blue
Team Summit and I was like, uh, I

00:08:25.388 --> 00:08:27.098
don't really have a talk in mind.

00:08:27.098 --> 00:08:27.488
So I've

00:08:27.563 --> 00:08:28.073
Josh Mason: Oh, cool.

00:08:28.268 --> 00:08:30.818
Tom Dejong: out topics that I
could, could do for future talks.

00:08:31.058 --> 00:08:33.518
Um, and I would love to speak
at a conference someday in the

00:08:33.518 --> 00:08:37.388
future, but need to get that
talk, uh, idea figured out first.

00:08:43.973 --> 00:08:44.453
Josh Mason: Yeah.

00:08:45.233 --> 00:08:49.028
Wade Wells: I, I got asked to do a
training on triage, so exactly what

00:08:49.028 --> 00:08:50.318
you're talk about talking about.

00:08:50.318 --> 00:08:55.808
And I built out the outline and then I
pretty much realized, I'm like, okay,

00:08:55.808 --> 00:08:57.698
this is like a good 16 hour training.

00:08:58.058 --> 00:09:00.488
And I'm like, I don't wanna
build out the labs for this.

00:09:00.578 --> 00:09:04.508
That's where I stopped uh, I had
to go tell the person like, Hey,

00:09:04.508 --> 00:09:05.588
I don't wanna do this anymore.

00:09:05.588 --> 00:09:06.698
Like, I don't have enough time.

00:09:07.148 --> 00:09:10.058
But it's honestly, like you said,
there isn't as much out there.

00:09:10.058 --> 00:09:12.878
I remember like when I started out,
there was no blue team training.

00:09:12.878 --> 00:09:14.858
It was all geared towards
red teamers, right?

00:09:15.128 --> 00:09:17.468
Like OSCP, all that type of stuff.

00:09:17.708 --> 00:09:21.128
And that was, hasn't really been since
like probably until like three, five

00:09:21.128 --> 00:09:25.028
years, three to five years ago is when
all these blue team stuff, more blue team

00:09:25.028 --> 00:09:26.588
oriented training started coming out.

00:09:27.038 --> 00:09:29.588
I remember like boss of the
SOC was like one of the first.

00:09:29.588 --> 00:09:33.308
like real blue team CTFs I
competed in, which is Splunk.

00:09:34.448 --> 00:09:34.868
Yeah.

00:09:34.898 --> 00:09:39.128
so it's a lot harder to do and
usually you have to build some type of

00:09:39.233 --> 00:09:41.393
Tom Dejong: Yeah, no, putting
together a whole class sounds

00:09:41.468 --> 00:09:42.098
Wade Wells: spin up two

00:09:42.113 --> 00:09:42.533
Tom Dejong: very,

00:09:42.668 --> 00:09:43.118
Wade Wells: and have one

00:09:43.163 --> 00:09:44.453
Tom Dejong: labor intensive.

00:09:44.513 --> 00:09:45.293
I was just listening to

00:09:45.293 --> 00:09:46.043
Josh Mason: You need that.

00:09:46.073 --> 00:09:49.103
Tom Dejong: Hayden last night,
and I was, he was talking, I think

00:09:49.103 --> 00:09:52.643
he said that he had way too much
content and I was like, oh man.

00:09:52.643 --> 00:09:54.713
I did not expect there
to be too much content,

00:09:59.273 --> 00:09:59.543
but yeah.

00:10:03.323 --> 00:10:06.143
Josh Mason: It's easy to, uh,
build your scope out a little

00:10:06.143 --> 00:10:07.703
too big for building training.

00:10:07.778 --> 00:10:08.048
Tom Dejong: makes

00:10:08.093 --> 00:10:13.193
Josh Mason: I've, uh, been in
that situation before, but, um.

00:10:17.648 --> 00:10:21.698
Where do you, uh, where do you
see yourself going in cyber now

00:10:21.698 --> 00:10:23.888
that you've started down the path?

00:10:23.918 --> 00:10:28.028
Is it one of those, you, you're at a
pen testing company, that's what Black

00:10:28.028 --> 00:10:31.988
Hills is known for, but you're working
things in the SOC and, uh, working

00:10:31.988 --> 00:10:37.388
alongside some of, I think some of the
best teachers in the industry there.

00:10:39.053 --> 00:10:44.153
But you're still kind of new to
cyber and yet you're killing it.

00:10:44.588 --> 00:10:45.578
Tom Dejong: yeah, man.

00:10:45.578 --> 00:10:46.958
I always struggle with this question.

00:10:46.958 --> 00:10:49.118
Same with like, what are, where
do you see yourself in five

00:10:49.118 --> 00:10:50.768
year questions In my mind.

00:10:51.723 --> 00:10:54.963
I just would take any cyber
position I could take and, you

00:10:54.963 --> 00:10:56.763
know, it's all learning experiences.

00:10:56.823 --> 00:10:59.613
Uh, man, who knows, maybe I
will go to the red team someday.

00:10:59.703 --> 00:11:03.663
Uh, and all this blue team experience
will be useful when that day comes.

00:11:03.663 --> 00:11:07.753
But, but for right now, um, yeah,
I'm just kind of taking it as, as.

00:11:08.058 --> 00:11:09.198
Taking it as it comes.

00:11:09.258 --> 00:11:11.298
Uh, the sock has been interesting.

00:11:11.328 --> 00:11:14.628
Uh, being pulled in on those IR
engagements was really interesting too.

00:11:14.718 --> 00:11:18.858
Uh, so, so, uh, you know, I'm,
I'm definitely open to helping

00:11:18.858 --> 00:11:20.028
with those in the future.

00:11:20.148 --> 00:11:23.718
Uh, I haven't really done very much
threat hunting, but threat hunting

00:11:23.838 --> 00:11:25.308
does seem pretty interesting.

00:11:25.783 --> 00:11:29.233
Um, but yeah, I don't know if I,
if somebody offered me a chance

00:11:29.233 --> 00:11:33.463
to do a red team job, I mean it
would definitely be, uh, pretty

00:11:33.463 --> 00:11:35.443
interesting to go in there and do that.

00:11:35.443 --> 00:11:38.413
'cause I feel like the purple
team stuff seems really important.

00:11:38.773 --> 00:11:41.743
Uh, so I mean, it would be awesome
to be able to build out on that more.

00:11:48.318 --> 00:11:48.858
Hmm.

00:11:49.748 --> 00:11:49.928
Wade Wells: What

00:11:49.968 --> 00:11:52.788
Tom Dejong: Oh man, it's
gotta be being curious.

00:11:52.928 --> 00:11:53.108
Wade Wells: like

00:11:53.118 --> 00:11:55.128
Tom Dejong: I feel like you're
constantly, you just constantly

00:11:55.128 --> 00:11:56.358
need to be learning stuff.

00:11:56.388 --> 00:12:00.318
Uh, so, so I feel like that's a
very good skill for soc analysts to

00:12:00.318 --> 00:12:05.328
have, uh, to just be wanting to know
and get to the bottom of things.

00:12:05.538 --> 00:12:08.933
Uh, 'cause uh, you know, there can
be some resilience in that too.

00:12:08.933 --> 00:12:12.593
Like, I, I'll get frustrated if
I can't figure it out, and I'll

00:12:12.593 --> 00:12:15.713
just, I just will have that drive
to keep wanting to push and push.

00:12:16.133 --> 00:12:19.943
Uh, so I'd say that's, that's gotta
be one of the more important ones.

00:12:27.468 --> 00:12:27.688
Yep.

00:12:27.858 --> 00:12:28.148
Wade Wells: Okay.

00:12:28.803 --> 00:12:33.453
Uh, so you've, you've been analyst
for like three years now, pretty much.

00:12:33.693 --> 00:12:34.683
What are your favorite

00:12:34.808 --> 00:12:35.228
Tom Dejong: boy.

00:12:35.463 --> 00:12:36.033
Wade Wells: to work then?

00:12:36.093 --> 00:12:38.948
Like, what's your, what's
your niche you would say?

00:12:39.818 --> 00:12:40.058
Tom Dejong: oh.

00:12:40.058 --> 00:12:41.018
This is a hard question.

00:12:41.258 --> 00:12:42.308
Oh, let's see here.

00:12:42.728 --> 00:12:43.538
I do,

00:12:49.028 --> 00:12:49.658
Josh Mason: Is it,

00:12:51.938 --> 00:12:55.388
do you guys get the option of like
picking which tickets you're gonna

00:12:55.388 --> 00:12:58.238
work or is it like auto assigned?

00:12:58.613 --> 00:12:58.853
Tom Dejong: Yep.

00:12:58.883 --> 00:13:00.173
We recently made a change

00:13:00.368 --> 00:13:02.408
Josh Mason: Because that would
be like one of those things.

00:13:02.813 --> 00:13:04.523
Tom Dejong: so, so
that's been newer for us.

00:13:04.523 --> 00:13:08.363
But in the past, I'd say for the majority
of the time I've been here, it's been just

00:13:08.393 --> 00:13:12.203
kind of a sign yourself and, you know,
I'd always try and take ones that I didn't

00:13:12.203 --> 00:13:14.153
know so I can figure out how to do it.

00:13:14.153 --> 00:13:14.393
But I.

00:13:15.593 --> 00:13:19.883
Oh man, I always like the easy ones,
like suspicious iso file downloads.

00:13:19.883 --> 00:13:22.973
'cause you can just go to the event
log fifteens and see where it was

00:13:22.973 --> 00:13:24.893
downloaded from most of the time.

00:13:24.983 --> 00:13:30.113
But nowadays, I mean the high risk Azure
logins can be pretty interesting to do.

00:13:30.503 --> 00:13:30.893
Uh, you

00:13:30.908 --> 00:13:31.118
Wade Wells: Yep.

00:13:31.253 --> 00:13:33.083
Tom Dejong: checking for
all of the login history.

00:13:33.113 --> 00:13:37.403
I don't, there's part of me that hates
doing 'em, but it is nice because it has

00:13:37.403 --> 00:13:41.123
so much of the data and you know, you
can go and kind of map out what happened.

00:13:41.453 --> 00:13:44.123
Um, but you know, I kind of
take 'em all as they come.

00:13:45.128 --> 00:13:46.133
It's hard to say the favorite.

00:13:51.323 --> 00:13:52.388
Wade Wells: I think the majority of.

00:13:53.408 --> 00:13:55.808
The majority of the socks that
I've worked in have all like,

00:13:56.108 --> 00:13:57.518
exactly like alert comes in.

00:13:57.518 --> 00:13:58.718
It's whoever grabs it, grabs it.

00:13:58.748 --> 00:14:00.968
There's no particular rhyme or reason.

00:14:00.968 --> 00:14:05.858
So usually what happens is the people
who have who, who know, have the

00:14:05.858 --> 00:14:09.338
knowledge to do a particular alert
that's a little bit easier, almost

00:14:09.338 --> 00:14:12.488
always gravitate towards those ones
so they can close them out real quick.

00:14:13.613 --> 00:14:16.883
I remember like one of the last socks
I worked at, I was one of the only

00:14:16.883 --> 00:14:19.193
guys who was heavy EDR experience.

00:14:19.523 --> 00:14:22.013
So I would always be like, Hey
Wade, do you get all the EDR alerts?

00:14:22.013 --> 00:14:23.993
And I'm like, I'm like, you guys
get some of these, like, you

00:14:23.993 --> 00:14:25.163
guys need to figure this out.

00:14:25.553 --> 00:14:30.323
Uh, but it's grabbing the wrong, or
grabbing the ones that you're weakest

00:14:30.323 --> 00:14:32.908
against is usually pretty time consuming.

00:14:32.963 --> 00:14:35.003
But do you like write

00:14:35.078 --> 00:14:35.618
Tom Dejong: Oh yeah.

00:14:35.708 --> 00:14:36.488
Yes, I do.

00:14:36.548 --> 00:14:36.818
And,

00:14:36.833 --> 00:14:37.103
Wade Wells: what you

00:14:37.178 --> 00:14:39.848
Tom Dejong: just real quick on
that, so one of the interns,

00:14:39.923 --> 00:14:40.133
Wade Wells: or the

00:14:40.178 --> 00:14:43.538
Tom Dejong: that he's, he was recently
become a full-time, uh, employee, but

00:14:43.808 --> 00:14:46.868
you know, he was, he was saying that
he's liking this round robin because.

00:14:47.483 --> 00:14:50.003
You know, like you were saying,
they'd gravitate towards not doing

00:14:50.003 --> 00:14:52.973
alerts that they didn't know about,
but now he's kind of forced to do it.

00:14:52.973 --> 00:14:56.633
So, uh, you know, he says that he's
been learning a lot from kind of

00:14:56.633 --> 00:14:58.223
having it forced upon him to do it.

00:14:58.223 --> 00:15:03.173
But, uh, sorry, do you mind
repeating that question again?

00:15:04.043 --> 00:15:05.093
I got sidetracked there.

00:15:09.648 --> 00:15:09.768
Hmm.

00:15:10.733 --> 00:15:12.503
Wade Wells: That was about
like, no, you're all good.

00:15:12.503 --> 00:15:14.963
Like, do you, uh, do you
take notes or anything?

00:15:14.963 --> 00:15:18.083
Like how, how do you like improve
the process as you're doing it?

00:15:18.083 --> 00:15:18.323
Right?

00:15:18.323 --> 00:15:19.253
Because if you're

00:15:19.373 --> 00:15:19.673
Tom Dejong: Yes.

00:15:19.913 --> 00:15:20.153
Okay.

00:15:20.303 --> 00:15:20.693
Yes.

00:15:21.023 --> 00:15:21.473
Wade Wells: and you don't

00:15:21.623 --> 00:15:22.283
Tom Dejong: I feel like I'm

00:15:22.433 --> 00:15:23.003
Wade Wells: usually

00:15:23.063 --> 00:15:26.573
Tom Dejong: the BHIS SOC for
having really detailed, uh, notes.

00:15:26.573 --> 00:15:30.623
So, so when I started, uh, you
know, there was a i'd, I'd try

00:15:30.623 --> 00:15:32.243
and find tickets that, you know.

00:15:32.993 --> 00:15:37.073
Explain why you came to these conclusions
and like what you did to go check.

00:15:37.163 --> 00:15:40.883
Um, and, you know, there were some
analysts that had really good tickets.

00:15:40.883 --> 00:15:43.823
There were some analysts that, you
know, they, they, they knew their

00:15:43.823 --> 00:15:46.433
stuff, but they didn't necessarily
explain their thought process.

00:15:46.433 --> 00:15:49.973
So, so in my head it was like,
I need to make sure that these

00:15:49.973 --> 00:15:51.533
tickets I'm doing are detailed.

00:15:51.798 --> 00:15:57.678
So that new analyst can come see my
work and say, okay, he went and checked

00:15:57.738 --> 00:16:00.168
this, uh, to come to this conclusion.

00:16:00.228 --> 00:16:04.668
Uh, so, so I've always been pretty big
proponent of trying to, uh, you know, make

00:16:04.668 --> 00:16:10.158
my logic easy to follow and, uh, you know,
for the next analyst down in the line.

00:16:10.248 --> 00:16:15.018
Um, and then, you know, the documentation,
I'm always trying to document things, you

00:16:15.018 --> 00:16:16.608
know, did we get that customer saying.

00:16:17.103 --> 00:16:19.743
Yeah, this software is approval
that's going automatically

00:16:19.743 --> 00:16:21.003
right in the knowledge base.

00:16:21.063 --> 00:16:24.123
Um, so, so I've always been big
on that type of stuff, for sure.

00:16:30.333 --> 00:16:30.843
Mm-hmm.

00:16:31.443 --> 00:16:33.783
Wade Wells: It's super important,
uh, especially with like writing

00:16:33.933 --> 00:16:35.813
a description down of exactly
what you did and how you do it.

00:16:36.518 --> 00:16:40.778
Uh, a lot of the times, so I know
traditional stems right back in the

00:16:40.778 --> 00:16:43.808
day, like they would limit that you
couldn't throw images and stuff.

00:16:43.808 --> 00:16:46.718
Now, but now today's when most
people are working in soars,

00:16:47.018 --> 00:16:48.908
I know you guys work in tides.

00:16:48.908 --> 00:16:50.018
I also work in tides.

00:16:50.663 --> 00:16:54.503
Uh, throwing images in there of exactly
all the evidence you saw or where you,

00:16:54.503 --> 00:16:58.733
where you went, uh, like that just helps
leaps and bounds, not just like the newer

00:16:58.733 --> 00:17:02.813
people that have like, that are working
under you, but like to spin someone up,

00:17:03.143 --> 00:17:06.383
that's someone that's brand new, even if
they are decently experienced, for you

00:17:06.383 --> 00:17:07.943
to show the example is very important.

00:17:07.943 --> 00:17:12.203
So I would highly, highly
suggest you, uh, continue

00:17:12.353 --> 00:17:13.793
Tom Dejong: I could stop
myself at this point.

00:17:13.793 --> 00:17:15.203
That would be, that would go against

00:17:15.443 --> 00:17:16.103
Wade Wells: it will help

00:17:16.133 --> 00:17:19.193
Tom Dejong: fiber in my body to
not be taking detailed notes.

00:17:26.333 --> 00:17:26.933
Wade Wells: Oh, I don't know.

00:17:27.263 --> 00:17:33.773
It's real, real easy to go down the,
uh, down the sarcastic, uh, beard

00:17:33.773 --> 00:17:35.663
Tom Dejong: Yeah, I could
see exactly how that happens.

00:17:35.783 --> 00:17:36.143
Wade Wells: Right.

00:17:36.233 --> 00:17:36.683
Tom Dejong: I, see,

00:17:37.523 --> 00:17:38.993
Wade Wells: I've seen the
best of 'em, but who knows.

00:17:42.308 --> 00:17:42.598
Yeah.

00:17:44.033 --> 00:17:44.333
Josh Mason: Yep.

00:17:45.563 --> 00:17:51.143
Is there, was it something that, uh, you,
you had to teach yourself on how to take

00:17:51.143 --> 00:17:55.733
your, the notes that you liked, or, uh,
was it part of the onboarding process?

00:17:55.958 --> 00:17:56.678
Tom Dejong: naturally to me.

00:17:56.678 --> 00:17:58.598
I didn't really necessarily need to do it.

00:17:58.628 --> 00:18:02.078
Well, and you know, another part of it
is, and I tell this to all the interns,

00:18:02.078 --> 00:18:03.668
I mentioned it in webcast, I've done.

00:18:04.388 --> 00:18:07.328
It really helps me to
write everything out.

00:18:07.328 --> 00:18:10.718
So, so when I'm trying to understand a
problem and I just write down, all right,

00:18:10.718 --> 00:18:15.128
this user did this, this and this, I'll
try and like summarize it or something.

00:18:15.218 --> 00:18:18.428
Um, so, and once I get it all out
there and write it into whatever

00:18:18.428 --> 00:18:22.178
ticketing system I'm using I
feel like it just makes it click.

00:18:22.238 --> 00:18:26.828
And one of the people that was, uh, one
of the senior analysts, you know, he'd

00:18:26.828 --> 00:18:28.778
say, I'd, I'd be like, Hey, do you mind.

00:18:29.268 --> 00:18:33.558
Doing like an internal escalation on this
and see, see if you agree with my logic.

00:18:34.038 --> 00:18:35.298
And then he would be like, well.

00:18:36.338 --> 00:18:39.938
And, uh, I guess this kind of sparked
the, me wanting to take, or like,

00:18:40.058 --> 00:18:41.678
at least break down what I'm seeing.

00:18:41.978 --> 00:18:45.398
He'd ask me like, well, what are you
seeing here that's actually malicious?

00:18:45.428 --> 00:18:48.668
Because, you know, when you start out,
you think everything looks malicious.

00:18:48.758 --> 00:18:50.948
Uh, so you kinda have to
take a step back from that.

00:18:50.948 --> 00:18:53.798
So, so maybe, maybe a little
bit of guidance from him.

00:18:53.798 --> 00:18:54.368
He helped.

00:18:54.428 --> 00:18:58.298
Uh, but I, I do feel like it comes
naturally to me just to want to try and

00:18:58.538 --> 00:19:00.578
break it down and put it all out there.

00:19:08.588 --> 00:19:11.978
Wade Wells: So with that, where does your,
how do you start off your hypothesis when

00:19:11.978 --> 00:19:13.388
you get an alert, do you automatically

00:19:13.538 --> 00:19:15.728
Tom Dejong: Nowadays, I do
not think everything looks,

00:19:15.818 --> 00:19:16.508
Wade Wells: that it isn't

00:19:16.658 --> 00:19:17.468
Tom Dejong: right off the bat.

00:19:17.498 --> 00:19:17.918
Um,

00:19:17.948 --> 00:19:19.058
Wade Wells: Or do you do like competing?

00:19:19.328 --> 00:19:22.148
Tom Dejong: I always try and go
to the detection logic at least,

00:19:22.148 --> 00:19:25.568
and then see like, okay, so what,
what exactly triggered this alert?

00:19:25.568 --> 00:19:27.398
And then I usually will build from there.

00:19:27.458 --> 00:19:31.328
Um, or I'll pull up an a pass
ticket or something, see if this

00:19:31.328 --> 00:19:32.438
has been encountered before.

00:19:32.438 --> 00:19:35.378
So, I don't know, it's kind of hard.

00:19:35.378 --> 00:19:38.708
I'll, I'll look at the executables
involved or you know, what, whatever

00:19:38.708 --> 00:19:41.738
executable or file is involved, and
then I'll kind of go from there.

00:19:41.798 --> 00:19:46.238
Uh, you know, nowadays with ai, I'll put
something like that in there and just be

00:19:46.238 --> 00:19:47.738
like, Hey, what do you think about this?

00:19:48.128 --> 00:19:49.898
Um, and I find that gives me a lot of.

00:19:49.973 --> 00:19:51.533
Places to pivot to as well.

00:19:51.533 --> 00:19:56.063
So, so, no, I wouldn't say I, I definitely
don't think everything's suspicious.

00:19:56.063 --> 00:19:59.903
That's something, I mean, right in,
in the beginning I was, I was feeling

00:19:59.903 --> 00:20:02.843
that way about everything, but now
I've seen so many false positives

00:20:02.843 --> 00:20:06.713
and normal activity and, you know,
software that acts like malware, uh,

00:20:06.713 --> 00:20:08.753
it, it's not really surprising to me.

00:20:08.753 --> 00:20:12.743
So, so I feel like, uh, you know, just
after, during doing cursory research,

00:20:12.743 --> 00:20:16.583
then I'll start kinda looking into it
and, you know, figure out does this

00:20:16.583 --> 00:20:18.443
seem like something weird or whatnot?

00:20:27.603 --> 00:20:28.083
Josh Mason: Interesting.

00:20:28.183 --> 00:20:30.973
Wade Wells: I know there's a,
there's a project somewhere,

00:20:32.713 --> 00:20:34.088
I can't remember where it is.

00:20:35.333 --> 00:20:39.503
But it's a list of pro, it's a list of
processes that do things like malware.

00:20:39.963 --> 00:20:39.993
Josh Mason: Ooh.

00:20:40.313 --> 00:20:44.153
Wade Wells: Uh, like, like, uh,
one, the one I can remember off

00:20:44.153 --> 00:20:47.483
the top of my head is like Global
Protect, which is Palo Alto's.

00:20:47.483 --> 00:20:48.683
VPN runs.

00:20:48.683 --> 00:20:49.343
Who Am I?

00:20:49.373 --> 00:20:50.093
Constantly.

00:20:50.423 --> 00:20:52.043
It's like, why, why are you running?

00:20:52.043 --> 00:20:52.553
Who am I?

00:20:52.583 --> 00:20:55.433
But, uh, so much of it out there.

00:20:55.913 --> 00:20:58.163
Uh, you did allude to using ai.

00:20:58.193 --> 00:20:59.483
What's your feelings on it right now,

00:20:59.873 --> 00:21:02.753
Tom Dejong: so I will start
this by saying I'm not super

00:21:02.753 --> 00:21:04.523
AI savvy or anything like that.

00:21:04.553 --> 00:21:08.753
Uh, there's been, there's been a bit of
a push at BHIS to start using it more.

00:21:08.843 --> 00:21:11.483
Uh, so, so I've really
been trying to use it.

00:21:11.543 --> 00:21:14.993
Uh, I'm, I'm having to like force
myself to use it a lot of times,

00:21:14.993 --> 00:21:17.783
but I, I guess it's kind of becoming
second nature at this point.

00:21:17.813 --> 00:21:22.103
Uh, but you know, I use it mainly
for helping with investigations.

00:21:22.103 --> 00:21:24.023
I'll use it for like polishing up.

00:21:24.413 --> 00:21:29.393
Uh, messages I'm sending to clients, but
we're starting to get some cool, like, uh,

00:21:30.233 --> 00:21:33.293
AI capabilities to make detection logic.

00:21:33.353 --> 00:21:35.633
Uh, so I'll try and do it too
for like making sure I have

00:21:35.633 --> 00:21:36.923
the right syntax and things.

00:21:37.733 --> 00:21:39.173
I feel like AI is.

00:21:39.218 --> 00:21:42.038
It's gonna be here to say I'm
not worried about it taking

00:21:42.038 --> 00:21:43.538
my job or anything like that.

00:21:43.598 --> 00:21:45.608
Uh, you know, it's another
tool in the tool belt.

00:21:45.938 --> 00:21:49.988
I am kind of sick of hearing about
it, but what can you do about that?

00:21:50.078 --> 00:21:54.488
Uh, it is a very cool tool overall though,
and I am excited to see where it goes.

00:21:54.488 --> 00:21:58.658
I think there was a, oh, there was some
webcast where they were talking about.

00:21:58.718 --> 00:22:03.338
I thought it was like a, a soc
analyst agent something where they

00:22:03.338 --> 00:22:04.778
kind of had it solving some issues.

00:22:04.778 --> 00:22:07.778
So, uh, that webcast
made it seem very cool.

00:22:07.898 --> 00:22:10.598
Uh, and I'm, I'm curious
to see where it goes to.

00:22:10.718 --> 00:22:13.898
Um, I think it's gonna, I think it's
really gonna help us in the long run.

00:22:20.968 --> 00:22:21.628
Wade Wells: Totally agree.

00:22:21.658 --> 00:22:22.348
Totally agree.

00:22:22.408 --> 00:22:25.378
I, I find it kind of interesting
right now how there's all these

00:22:25.378 --> 00:22:28.558
big sock companies or all these big
sock AI companies that are out there

00:22:28.558 --> 00:22:30.148
and they like, they bolt onto you.

00:22:30.548 --> 00:22:33.848
I think it's only a matter of
time to pretty much what happens

00:22:33.848 --> 00:22:37.988
to them happens to source where,
uh, all the swords would bolt on.

00:22:38.198 --> 00:22:42.008
But then all of a sudden the bigger
companies that own the Splunks,

00:22:42.038 --> 00:22:45.338
the CrowdStrike, all these,
they buy out all the source and

00:22:45.338 --> 00:22:46.688
then just have the motto attach.

00:22:46.868 --> 00:22:49.448
I think the same thing is either gonna
happen to the AI or they're gonna

00:22:49.448 --> 00:22:53.318
build the AI functionality into it,
uh, which we're, which we're already

00:22:53.318 --> 00:22:54.818
seeing with all the big security tools.

00:22:54.818 --> 00:22:56.528
They all say they got it on the roadmap.

00:22:56.588 --> 00:22:56.918
Josh Mason: Yep.

00:22:57.128 --> 00:22:58.388
Wade Wells: You would know
more about that, Josh.

00:22:58.778 --> 00:22:59.198
Josh Mason: Yeah.

00:22:59.258 --> 00:23:01.298
Uh, you're, you're right.

00:23:01.328 --> 00:23:04.238
Everyone is trying to work
it into every single product.

00:23:04.688 --> 00:23:11.108
Um, and I'm, I actually worry that,
uh, at the end of like, whatever season

00:23:11.108 --> 00:23:15.968
this is, uh, that our listeners are
gonna be like, we're tired of hearing

00:23:15.968 --> 00:23:20.108
about AI in blue teaming, but, um.

00:23:20.168 --> 00:23:22.583
Wade Wells: It does so well in
the, so well in the algorithm.

00:23:23.363 --> 00:23:26.003
I think it's, it's more important
to talk about, especially with

00:23:26.003 --> 00:23:27.953
people like Tom, I feel because.

00:23:28.703 --> 00:23:31.703
Everyone's saying the AI's
gonna take Tom's job like that.

00:23:31.703 --> 00:23:32.603
Like that's that.

00:23:33.018 --> 00:23:33.308
Josh Mason: Yeah.

00:23:33.443 --> 00:23:35.393
Wade Wells: to say it, but like, that's
like they're already gonna take, like

00:23:35.393 --> 00:23:36.893
as me as a detection engineer, right?

00:23:36.893 --> 00:23:39.533
Like I've seen great ones that
are doing exactly the same thing.

00:23:39.923 --> 00:23:41.483
It's, uh, but it's important.

00:23:41.843 --> 00:23:44.363
I don't think we blast about
too much about it, but I,

00:23:44.648 --> 00:23:45.008
Tom Dejong: No,

00:23:45.053 --> 00:23:45.923
Wade Wells: people's boots on the

00:23:46.208 --> 00:23:46.688
Tom Dejong: a good point.

00:23:47.003 --> 00:23:48.833
Wade Wells: uh, opinion
on it is a little better.

00:23:49.163 --> 00:23:49.613
Josh Mason: Yeah.

00:23:49.653 --> 00:23:49.953
Tom Dejong: go on.

00:23:50.363 --> 00:23:52.073
Josh Mason: We've just been
asking a lot of people.

00:23:55.343 --> 00:23:55.733
Yeah.

00:23:56.063 --> 00:24:01.163
It's cool to hear that, like, you're
not worried about it because I, I don't

00:24:01.163 --> 00:24:02.633
think we should be worried about it.

00:24:02.693 --> 00:24:08.423
Um, but a lot of people will point at,
oh, it's gonna take like the lowest jobs.

00:24:08.423 --> 00:24:08.483
Um,

00:24:10.528 --> 00:24:15.953
and in my opinion, that's where
you really need people to do stuff.

00:24:15.983 --> 00:24:19.583
Uh, triage on its own is, uh.

00:24:20.318 --> 00:24:23.558
It's difficult to do with automation.

00:24:24.248 --> 00:24:32.048
It's up there with like pen testing and,
uh, triaging vulnerabilities and, uh,

00:24:32.168 --> 00:24:34.148
you know, wearing the synex shirt today.

00:24:34.448 --> 00:24:36.548
Uh, they're working on it.

00:24:36.818 --> 00:24:39.858
Here's a product, but
there's not a lot of 'em.

00:24:40.803 --> 00:24:44.018
And, uh, you definitely still
need humans to do the pen testing.

00:24:44.043 --> 00:24:44.263
So.

00:24:45.713 --> 00:24:48.623
Or validation of what the agents find.

00:24:48.653 --> 00:24:55.613
So, yeah, uh, having an AI that leads into
a SOAR and just automates, uh, actions,

00:24:56.003 --> 00:25:01.163
um, it will be an interesting world
when people say, yeah, let's just do it,

00:25:01.298 --> 00:25:01.898
Tom Dejong: because they're

00:25:02.003 --> 00:25:02.633
Josh Mason: in my opinion.

00:25:02.648 --> 00:25:05.228
Tom Dejong: trying to replace
jobs with AI necessarily.

00:25:05.288 --> 00:25:09.188
Uh, you know, but I, I, I feel for
analysts that are at companies where,

00:25:09.278 --> 00:25:13.363
you know, the company is trying
to replace 'em with ai and I, I, I

00:25:13.368 --> 00:25:14.648
have similar feelings towards you.

00:25:14.648 --> 00:25:16.088
You know, we do need it down.

00:25:16.148 --> 00:25:16.298
Uh.

00:25:16.933 --> 00:25:17.683
In the soc.

00:25:17.713 --> 00:25:19.483
Um, it's, it's very useful.

00:25:19.513 --> 00:25:22.063
Um, but yeah, I've, and I
haven't ever been too worried

00:25:22.063 --> 00:25:24.223
about it taking jobs in general.

00:25:24.313 --> 00:25:29.533
Um, I feel like there's a lot of hype
around it and I, I, I, just don't

00:25:29.533 --> 00:25:31.783
see it t fully taken over the job.

00:25:31.903 --> 00:25:36.013
Um, you know, the triage is difficult
and yeah, I, from, from what I've

00:25:36.013 --> 00:25:39.073
seen, it does seem like it'll have
some great impacts on us, bud.

00:25:39.518 --> 00:25:40.958
Yeah, I'm curious to see where it goes.

00:25:41.138 --> 00:25:45.008
And I, myself am trying to be more
creative with it too, because I've

00:25:45.008 --> 00:25:47.288
always felt I'm a very analytical person.

00:25:47.288 --> 00:25:51.338
Not as much creativity, but uh,
you know, just seeing these, seeing

00:25:51.338 --> 00:25:52.418
these things people are doing.

00:25:52.418 --> 00:25:56.378
I'm, I, I really am trying to change
my mindset about it and say, well, how

00:25:56.378 --> 00:25:58.988
can I use AI to perform at this task?

00:25:59.018 --> 00:25:59.708
Uh, you know.

00:26:08.503 --> 00:26:12.823
Josh Mason: One thing I've been
wondering about as someone new, uh, to

00:26:12.823 --> 00:26:16.273
cyber working at Black Hills, I know.

00:26:16.718 --> 00:26:20.648
You got access to the Antis
Siphon courses, but is there

00:26:20.648 --> 00:26:26.648
other training, um, that you felt
has been valuable for, uh, your

00:26:26.723 --> 00:26:27.923
Tom Dejong: interesting question.

00:26:28.058 --> 00:26:29.138
Josh Mason: these past couple years?

00:26:29.963 --> 00:26:33.173
Tom Dejong: to be completely honest with
you, I haven't done, I've mainly only

00:26:33.173 --> 00:26:35.003
been doing the antis safe in training.

00:26:35.063 --> 00:26:38.963
Uh, since I've been at BHIS,
it's, it's hard to, uh, refute it

00:26:38.963 --> 00:26:41.153
because it's, because it's free.

00:26:43.478 --> 00:26:43.868
Josh Mason: Yeah.

00:26:43.913 --> 00:26:44.333
Tom Dejong: yeah.

00:26:44.363 --> 00:26:44.663
Yep.

00:26:44.693 --> 00:26:45.923
No, I've learned some good stuff

00:26:45.953 --> 00:26:47.633
Josh Mason: There's plenty
of it and it's good stuff.

00:26:47.723 --> 00:26:48.143
Yeah.

00:26:48.323 --> 00:26:50.933
Tom Dejong: I was taking a training,
I definitely would want to start

00:26:50.933 --> 00:26:52.673
learning more about cloud stuff.

00:26:52.733 --> 00:26:56.723
I mean, that seems, that seems to
be where the industry is going.

00:26:56.813 --> 00:26:57.983
And, uh, yeah.

00:26:57.983 --> 00:27:01.883
I got, I, I, I, I think that if you could
find some good cloud courses, that would

00:27:01.883 --> 00:27:04.133
be very good for SOC analysts now because.

00:27:04.898 --> 00:27:09.188
I can, I can look around at the
logs in AWS and Azure, uh, and, you

00:27:09.248 --> 00:27:10.628
know, kind of know what's going on.

00:27:10.628 --> 00:27:14.588
But, uh, I definitely don't feel as
comfortable with it as I would, uh, uh,

00:27:14.588 --> 00:27:16.298
looking at a Windows host or whatnot.

00:27:16.298 --> 00:27:18.968
So, so that's something that I
definitely would like to take

00:27:18.968 --> 00:27:20.498
more of is some cloud courses.

00:27:20.498 --> 00:27:24.398
But I, I can't say I have any
recommendations for courses I've taken.

00:27:33.068 --> 00:27:36.968
Josh Mason: So that's
really, uh, useful insight.

00:27:36.968 --> 00:27:41.438
Um, I, I figure if someone has
found simply defensive, there's

00:27:41.438 --> 00:27:45.128
a good chance that they know
that like Wade's got a class on.

00:27:46.178 --> 00:27:47.168
Antis Siphon.

00:27:47.168 --> 00:27:50.528
And a lot of our guests,
especially those for Black Hills,

00:27:50.608 --> 00:27:50.968
Tom Dejong: Siphon

00:27:51.098 --> 00:27:52.598
Josh Mason: have courses on Antis Siphon.

00:27:52.918 --> 00:27:53.428
Tom Dejong: on there.

00:27:53.518 --> 00:27:54.448
Uh, you know, I've, I've

00:27:54.518 --> 00:27:55.813
Josh Mason: not sponsored by the way.

00:27:56.008 --> 00:27:57.598
Tom Dejong: Team one, so
they're good at my job.

00:27:57.598 --> 00:27:59.548
But, sorry, I was thinking

00:27:59.853 --> 00:28:00.143
Josh Mason: Yeah,

00:28:00.298 --> 00:28:01.528
Tom Dejong: anything that's not antis.

00:28:03.568 --> 00:28:05.128
No, there's some great ones on there.

00:28:05.128 --> 00:28:06.773
People should definitely, oh.

00:28:08.468 --> 00:28:09.098
Josh Mason: right, right.

00:28:09.098 --> 00:28:10.658
No, that's what I was asking for.

00:28:11.318 --> 00:28:11.468
Yeah.

00:28:13.628 --> 00:28:13.838
Yeah.

00:28:13.868 --> 00:28:14.408
So you're good.

00:28:14.438 --> 00:28:14.888
You're good.

00:28:16.028 --> 00:28:22.598
Um, one of the things we like to ask
folks, uh, at the end of the episodes,

00:28:23.828 --> 00:28:28.298
what's like one piece of advice
you would have for any blue team?

00:28:28.793 --> 00:28:33.743
Tom Dejong: Um, I think, think, you know,
just, uh, just know that you're gonna

00:28:33.743 --> 00:28:35.873
make mistakes out there and that's okay.

00:28:35.903 --> 00:28:40.193
We all make mistakes, uh, and, you know,
try and use them as learning experiences.

00:28:40.673 --> 00:28:43.643
Uh, I've, I, you know, I get
nervous that, oh, I'm gonna miss.

00:28:44.123 --> 00:28:47.183
Uh, threat and you know, it,
I, it'll sit with me for the

00:28:47.183 --> 00:28:48.293
rest of the day or whatnot.

00:28:48.293 --> 00:28:52.403
So, so just trying to be able to take
mistakes as they come and move along

00:28:52.403 --> 00:28:54.833
and, you know, nobody knows everything.

00:28:54.833 --> 00:28:57.353
This is such a, a vast field.

00:28:57.773 --> 00:28:59.633
Um, you know, it's important.

00:29:00.518 --> 00:29:03.308
it it's important to be able to
utilize the people around you.

00:29:03.308 --> 00:29:07.148
Like, you know, you could say, Wade,
Wade knows a lot about EDR stuff.

00:29:07.148 --> 00:29:09.608
Well, while I'm doing this
ticket, let's go to him.

00:29:09.758 --> 00:29:15.068
Um, and you know, I'd say, I'd say
that when you feel, if you feel like

00:29:15.068 --> 00:29:18.398
you're making a mistake, you know,
run it by a teammate that knows more

00:29:18.428 --> 00:29:20.558
about it and try and learn from them.

00:29:20.798 --> 00:29:24.038
Um, and you'll, I feel like I learn
something new every single day.

00:29:24.128 --> 00:29:26.648
Uh, so I try and come at
it from that perspective.

00:29:26.648 --> 00:29:28.718
But alright to make mistakes.

00:29:34.398 --> 00:29:34.618
Yep.

00:29:35.988 --> 00:29:36.208
Yep.

00:29:36.278 --> 00:29:36.698
Wade Wells: a good one.

00:29:36.698 --> 00:29:38.078
You're not gonna catch everything, right?

00:29:38.108 --> 00:29:39.243
Every now and then
something's gonna slip by.

00:29:39.698 --> 00:29:39.818
Yeah,

00:29:41.903 --> 00:29:47.093
Josh Mason: I recently read
somewhere, uh, someone saying, uh,

00:29:47.183 --> 00:29:49.403
I'm continually surprised that the.

00:29:50.213 --> 00:29:51.953
Process of trial and error

00:29:52.253 --> 00:29:52.643
Tom Dejong: It can be

00:29:52.673 --> 00:29:53.693
Josh Mason: requires error.

00:29:53.813 --> 00:29:54.473
Tom Dejong: it happens.

00:29:54.653 --> 00:29:54.863
I,

00:29:55.433 --> 00:29:55.793
Josh Mason: So,

00:29:56.123 --> 00:29:56.423
Tom Dejong: that

00:29:56.453 --> 00:29:56.633
Josh Mason: yeah.

00:29:56.693 --> 00:29:59.783
Tom Dejong: it bothers me when I mess
up, but you know, it's, you just gotta

00:29:59.783 --> 00:30:02.093
take a step back and That's funny.

00:30:02.153 --> 00:30:03.503
I'll have to look more into that.

00:30:12.563 --> 00:30:15.023
Josh Mason: Well, Tom, thank
you so much for joining us.

00:30:15.083 --> 00:30:15.623
Uh.

00:30:16.553 --> 00:30:21.383
Folks, if you, uh, like the episode,
uh, like share, subscribe, do all those

00:30:21.383 --> 00:30:23.513
things and we'll see you on the next one.

00:30:26.258 --> 00:30:27.518
Wade Wells: See ya.

00:30:29.213 --> 00:30:29.393
Josh Mason: Yeah.

00:30:30.923 --> 00:30:31.013
Cool.