תעתיק 🔗
WEBVTT
00:00:02.879 --> 00:00:07.519
Hello and welcome to the Hack Responsibly Podcast, where we get to know NetSpy's technical leaders.
00:00:07.679 --> 00:00:15.279
I'm your host, Carl Foss, and today we'll be speaking with James Albany, the senior director that oversees network pen testing services here at NetSpy.
00:00:15.359 --> 00:00:20.000
I've gotten to know James pretty well over the years, and it was great catching up with him in this format.
00:00:20.239 --> 00:00:22.160
Here's my conversation with James.
00:00:23.199 --> 00:00:31.600
Welcome to Hack Responsibly, a NetSpy podcast focused on the experience of our NetSpy agents, including insights and trends in the cybersecurity industry.
00:00:31.760 --> 00:00:33.200
I'm your host, Carl Fawson.
00:00:33.359 --> 00:00:35.359
Today we have James Albany with us.
00:00:35.520 --> 00:00:38.079
James, you want to give everybody a quick intro about yourself?
00:00:38.640 --> 00:00:40.159
Yeah, hey, I'm James.
00:00:40.320 --> 00:00:44.079
I've uh been at NetSpy for a few years now.
00:00:44.159 --> 00:00:50.320
I'm a senior director of infrastructure testing and lead those efforts at NetSpy.
00:00:50.719 --> 00:00:51.439
Awesome.
00:00:51.759 --> 00:00:56.479
So uh you know, with Senior Director of Infrastructure, what have you been working on?
00:00:56.560 --> 00:00:58.719
Uh, what's kind of top of mind for you?
00:00:59.200 --> 00:01:02.719
Yeah, so right now that's focusing on two things primarily.
00:01:02.880 --> 00:01:09.280
That's how we can improve our uh continuous testing capabilities across various verticals.
00:01:09.760 --> 00:01:13.120
Um, so that's internal, external, cloud, etc.
00:01:13.760 --> 00:01:23.040
Um, and then uh focusing on automation efforts and how we can use AI to augment our testing success and speed.
00:01:23.519 --> 00:01:26.079
Well, those all sound like really cool things to be working on.
00:01:26.159 --> 00:01:28.959
Uh, how did you get your start in cybersecurity?
00:01:29.840 --> 00:01:36.239
Uh yeah, so I started as a SOC analyst actually and a managed security services provider.
00:01:36.480 --> 00:01:42.719
Um, and did that for about a year, got a lot of good experience on different technologies.
00:01:42.799 --> 00:02:05.359
Uh, we managed IAM, so got a lot of experience with Active Directory and got to manage RSA tokens and then uh gamut of technologies uh for managing alerts and uh in the SOC there, and then transferred into penetration testing about a year later, um getting into consulting.
00:02:05.680 --> 00:02:13.120
Yeah, I never knew that about you about the uh SOC side of things when we met, gosh, probably what, 10 years ago at this point, probably.
00:02:13.280 --> 00:02:13.599
Yeah.
00:02:13.919 --> 00:02:21.520
Uh yeah, you were at a different firm at that time and eventually came over to NetSpy here, but uh yeah, I didn't really know that about you.
00:02:21.680 --> 00:02:22.240
Very cool.
00:02:22.479 --> 00:02:23.039
Yeah, yeah.
00:02:23.199 --> 00:02:29.759
It was uh overnight shift, but it was it was getting started in the industry and it was my first foot in the door.
00:02:29.840 --> 00:02:41.120
So speaking of first feet in the door, uh you know, for people that are just starting their career, any advice that you would give to somebody that's early on in their cybersecurity career?
00:02:42.080 --> 00:02:48.800
Well, the uh the early job market is much different than when I entered the cybersecurity industry.
00:02:48.879 --> 00:03:03.280
So I guess like my classic response would be to look at sock jobs like I did and kind of get a feel for the defensive side of the industry and the security industry as a whole, how things are handled.
00:03:03.599 --> 00:03:17.919
But really today, um I think people need to think about how AI can impact their automation and the speed at which they do things and create tools and uh things like that.
00:03:18.240 --> 00:03:29.919
But I think that a big focus or big piece of advice I'd give to newcomers is to really focus on um the technical aspects under the hood of the things they're building.
00:03:30.080 --> 00:03:39.919
Um really understand what's happening under the hood so that you're able to know what AI is doing really well and what AI is not doing so well.
00:03:40.960 --> 00:03:41.840
That's good to hear.
00:03:41.919 --> 00:03:44.879
I think the fundamentals are absolutely important.
00:03:45.199 --> 00:03:50.719
Because yeah, to a certain degree, you can you can trust some of these models to give you the right thing out of it, right?
00:03:51.120 --> 00:03:59.039
But if you don't know enough of the fundamentals to do the gut check and be like, is this just a hallucination or is this like really a thing?
00:03:59.280 --> 00:04:06.960
Uh yeah, like if you don't know those core fundamentals, how do you know that you're actually reporting something that's real and valid, right?
00:04:07.280 --> 00:04:10.800
So getting that kind of under your belt first, I think that's super important.
00:04:11.120 --> 00:04:12.560
Yeah, exactly.
00:04:13.039 --> 00:04:20.079
So speaking of, did you kind of cut your teeth on that with your initial entry into the uh cybersecurity field?
00:04:20.160 --> 00:04:23.759
Or did you learn that you know prior to getting into that SOC job?
00:04:24.079 --> 00:04:42.879
Yeah, I think I I actually had a research internship in college that allowed me to kind of build an Active Directory environment from the ground up, and then building off of that in my first job as a SOC analyst, getting my hands on a bunch of different technologies and then researching how those work.
00:04:43.120 --> 00:04:55.120
And really, as I got into penetration testing, realizing how the defensive side works for that fundamental understanding of how these things are being intaked by teams.
00:04:55.519 --> 00:05:01.759
Um, and then yeah, just building on that fundamental understanding and then constantly learning.
00:05:02.000
Load full transcript
--> 00:05:07.040
I think earlier in the industry, there was a lot of focus on certifications.
00:05:07.279 --> 00:05:09.759
Uh, I think that's less and less now.
00:05:10.160 --> 00:05:16.560
Um, and there's just more information available to people for lower cost or free.
00:05:16.959 --> 00:05:34.639
But um yeah, I think just using those courses as learning material, not necessarily focusing on the certification, but making sure that you understand the information that those courses are displaying is really important for fundamental understanding.
00:05:35.040 --> 00:05:36.240
I'm really jealous.
00:05:36.399 --> 00:05:48.240
Uh, when I was in school, we were, I guess in the program I was in, we were very locked into just Linux only and you know, very open source-centric kind of things.
00:05:48.560 --> 00:06:00.959
And not that it didn't prepare us for the real world, but like outside of having a computer lab that happened to have Windows in it, like we didn't talk about Active Directory or Windows or programming for Windows necessarily.
00:06:01.199 --> 00:06:11.040
Like a lot of the computer science background that I had was really focused on like, yeah, you're gonna program in you know, C, C, Python, you know, stuff like that on a Linux system.
00:06:11.120 --> 00:06:13.600
Uh, so we never touched that.
00:06:13.759 --> 00:06:24.560
Uh, I think I really didn't get my Active Directory experience until I was out of school and worked for a smaller company where you know, uh, hey, we need somebody to you know manage the Active Directory environment.
00:06:24.720 --> 00:06:27.759
And okay, I can help out, I guess.
00:06:28.000 --> 00:06:29.600
And learned a lot.
00:06:29.680 --> 00:06:30.560
It was great.
00:06:30.800 --> 00:06:36.399
Uh, but you know, it was really more like in the job uh kind of experience.
00:06:36.720 --> 00:06:37.120
Yeah.
00:06:37.360 --> 00:07:09.040
Yeah, the professor at Penn State, Nick Jacoby, uh, he taught me a lot uh around that and he explained the kind of situation that colleges and universities go through with that, where it's really a timing thing of licensing combined with curriculum approval, where uh by the time that they're approved to give more concrete material around, like Active Directory users and computers for Windows 2008, all of a sudden that might be end of life, or they're moved on to 2012 and teaching the latest material.
00:07:09.279 --> 00:07:09.519
Yep.
00:07:09.839 --> 00:07:10.800
Which I understand.
00:07:10.959 --> 00:07:18.720
Um, so yeah, it was it was a really interesting and unique opportunity to get to work with him and really build that out for a research project.
00:07:19.120 --> 00:07:32.000
In terms of tools, techniques, other kind of you know, fun stuff that you've learned over the years here, do you have a specific technique or tool that you like to lean on or that you think is particularly fun to use?
00:07:33.360 --> 00:07:51.759
Um, I think on nowadays I am surprised to see how effective things like Pixie booting are and network boot functionality uh with things like SECM and config servers, uh being able to key in on that TFTP service on internal networks.
00:07:52.000 --> 00:07:52.319
Yep.
00:07:52.720 --> 00:07:57.040
Um I think otherwise I'll I'll kind of date myself with some of my go-tos.
00:07:57.439 --> 00:07:59.759
I think nowadays there's a lot of tools out, right?
00:08:00.000 --> 00:08:02.480
There's a lot of options to do a lot of things.
00:08:02.720 --> 00:08:10.399
Um, but before Bloodhound, I think my go-to was just using NetRPC in different ways for enumeration.
00:08:10.959 --> 00:08:17.839
Um I think I had just like a sheet of different net RPC loops that I would run to enumerate directory.
00:08:18.720 --> 00:08:21.519
I could probably dig up my old checklist for that.
00:08:21.839 --> 00:08:23.600
I probably still have that.
00:08:24.240 --> 00:08:24.639
Yeah.
00:08:24.959 --> 00:08:26.160
I'm gonna have to look for that one.
00:08:26.240 --> 00:08:46.159
I so it's a good thing that I'm not a betting person, because if you had said TFTP was gonna be as prevalent as it still is today, say five to ten years ago, when you know we were starting to see more of those attacks kind of pop up and actually having some pretty good luck with it, uh, I would have thought, oh no, the TFTP is gonna be gone.
00:08:46.240 --> 00:08:52.159
Like I thought that was already kind of just barely hanging on by a thread, uh, say 10 years ago.
00:08:52.240 --> 00:08:55.519
Uh, but it actually seemed to pick up a ton more of adoption over the years.
00:08:55.679 --> 00:09:00.720
And I get it, it's you know, practical, and there's a lot of different ways it can be implemented.
00:09:00.960 --> 00:09:05.360
And uh it's just interesting to hear how prevalent that still is these days.
00:09:05.759 --> 00:09:08.559
Yeah, it's uh open attack vector.
00:09:08.639 --> 00:09:19.279
I think a lot of it is um like we've been checking for it for years, like you say, but uh I think a lot of uh pen test groups might not check for it.
00:09:19.440 --> 00:09:25.919
It seems to be new information sometimes when um we're identifying these things.
00:09:26.320 --> 00:09:26.720
Yeah.
00:09:27.039 --> 00:09:30.720
And it definitely feels like something that's kind of evolved over the years.
00:09:30.799 --> 00:09:47.360
Uh speaking of things evolving over the years, what have you seen kind of as a shift in the overall threat landscape or potentially from testing methodology uh over, you know, we'll say your years in uh in the cybersecurity consulting space?
00:09:47.679 --> 00:09:49.120
There's a few perspectives here.
00:09:49.279 --> 00:09:56.320
I think the the biggest shift that I'm seeing is a focus on being able to operate continuously.
00:09:56.559 --> 00:10:17.120
So fixing that gap between point-and-time assessments if a new vulnerability is disclosed or a new service comes online um and having that tested, validated, make sure that
you you know if you are or not vulnerable to uh a newly disclosed issue uh and things like that.
00:10:17.279 --> 00:10:35.600
And then nowadays uh there's things like uh the mention of mythos coming out, and I think that an important perspective to realize is that we're not dealing with any new problems or new techniques with some of these AI evolutions.
00:10:35.759 --> 00:10:38.559
It's more just a fire hose effect.
00:10:38.639 --> 00:10:41.840
So it's just the issues are coming at us faster.
00:10:42.240 --> 00:10:48.559
Um, so like a year ago, two years ago, these vulnerabilities still existed.
00:10:48.799 --> 00:10:56.000
It's just now we're gonna be faster to know about them, which is overall a good thing for the security industry, right?
00:10:56.320 --> 00:11:01.519
Um, because there will be less vulnerabilities that threat actors have access to that we do not.
00:11:02.000 --> 00:11:07.440
Um, and we can know about those and patch those and um things like that.
00:11:07.759 --> 00:11:16.080
But I think that's a key perspective that's lost on people is that we're not really dealing with any new problems in the security industry.
00:11:16.320 --> 00:11:20.080
It's just more of a fire hose effect of them coming at us faster.
00:11:20.399 --> 00:11:28.240
Yeah, the volume that we're seeing with this and just the detection rates and the ease of being able to pull these things in.
00:11:28.320 --> 00:11:38.320
I totally agree with more of the kind of continuous approach of we have to be on top of these things because they're just they are coming at us at a fire hose pace.
00:11:38.639 --> 00:11:45.919
Uh do you feel like the time to proof of concept code is coming down?
00:11:46.159 --> 00:11:53.679
Because I feel like 10 years ago you would get a vulnerability to get introduced, and you might not see proof of concept code for six months to a year in some cases.
00:11:53.840 --> 00:11:55.919
Do you feel like that is starting to shrink?
00:11:56.320 --> 00:12:00.159
Yeah, and I think it will keep shrinking with things like mythos.
00:12:00.480 --> 00:12:14.080
I think that drastically shifts that and could probably take some denial of service vulnerabilities into full remote code execution, um, depending on the vulnerability and things like that.
00:12:14.399 --> 00:12:19.679
But uh also the shift of being able to develop checks for some of these vulnerabilities.
00:12:19.759 --> 00:12:35.759
So, say you use something like Nuclei or any POC, just being able to generate a check and validate that is a much quicker process now than it was six months ago, a year ago, and things like that.
00:12:36.159 --> 00:12:36.879
Oh, of course.
00:12:37.039 --> 00:12:43.759
Yeah, I I think the the big takeaway I'm getting here is that the timeframes are reducing overall, right?
00:12:44.080 --> 00:12:54.399
Time to detect the actual vulnerabilities themselves, time to get detections written as you know, new things are emerging, research gets put out there,
that kind of thing.
00:12:54.639 --> 00:13:01.519
And then time frames for remediation and just making sure that you know everything's buttoned up and patched as quick as possible.
00:13:01.759 --> 00:13:09.120
I think everything's just kind of compressing to a certain degree, uh, thanks to a lot of the AI stuff, which may be a good thing.
00:13:09.200 --> 00:13:12.240
Uh maybe the remediation part uh compressing a little bit.
00:13:12.320 --> 00:13:18.639
But when you start talking volume with the time to identification, you start blowing that out of the water a little bit.
00:13:18.879 --> 00:13:22.720
So yeah, it'll be interesting to see how this evolves in the next few years.
00:13:23.120 --> 00:13:34.080
So, you know, speaking from you know a client perspective and how things are evolving there, are you hearing any interesting things from clients lately or interesting asks that they have that might be pushing different directions?
00:13:34.559 --> 00:13:36.639
I think it's kind of the same vein.
00:13:36.720 --> 00:13:48.799
Uh, everyone is looking for how they can get continuous testing and then also um what we're doing with AI and how AI is being used.
00:13:48.879 --> 00:13:51.840
Um, we're having to use AI securely.
00:13:51.919 --> 00:14:02.320
We don't want to put any data in um AI workflows, but you can kind of abstract that with tool usage and things like that.
00:14:02.639 --> 00:14:22.000
So uh it's really just mainly questions around that speed, how we're using AI and how we're doing continuous testing, um, and how we're approaching those things to be able to rapidly identify these issues as they come out um over time.
00:14:22.399 --> 00:14:25.039
So it's it's definitely a move away.
00:14:25.279 --> 00:14:37.440
The industry is starting to move away from point-in-time mentality and more uh security programs that go on uh for longer periods of time.
00:14:37.840 --> 00:14:39.919
Yes, I would totally agree with that one.
00:14:40.159 --> 00:14:44.159
I have gotten some interesting questions regarding AI.
00:14:44.240 --> 00:14:48.399
Uh, kind of a like for better or worse, you know, how are you using AI?
00:14:48.559 --> 00:14:54.000
And it's almost like it's a requirement that you have to use it, even if it's the right tool for the job or not.
00:14:54.240 --> 00:14:58.480
Uh there's some mandates out there that folks need to be using AI.
00:14:58.559 --> 00:15:04.159
And I don't know if I always agree with it, because sometimes traditional automation is just the better choice.
00:15:04.240 --> 00:15:07.200
But yeah, AI it's useful in a lot of different cases.
00:15:07.360 --> 00:15:09.919
So it's interesting to get some of those questions.
00:15:10.399 --> 00:15:21.919
Yeah, it's it's interesting because AI is making us overall faster, but there's also situations where putting something at the tool level will be faster than putting it at the LLM level.
00:15:22.080 --> 00:15:37.840
Um, if you need quick defined response, like if
it's do X or Y, then the tool level is usually better than um making that at the AI level, um, just for speed and things like that.
00:15:38.320 --> 00:15:53.519
Yeah, I I think we are seeing a little bit of a shift where folks are focusing more on what can AI produce to help the automation, like you were talking about nuclei templates, uh, being able to produce those out of an AI and then utilize those in more traditional automations.
00:15:53.679 --> 00:15:55.120
I think that's really the way to go.
00:15:55.279 --> 00:16:05.440
Then instead of just sending the HTTP request in response over to the LLM to go, hey, process this and tell me if it's vulnerable, I think that's kind of a waste of AI resources.
00:16:05.600 --> 00:16:09.919
Like let's build actual templates to uh detect that instead.
00:16:10.080 --> 00:16:13.120
I think that's a little bit better focused, but that's my opinion.
00:16:13.440 --> 00:16:29.039
Yeah, and another shout out, I uh Jake Reynolds made a blog about how uh they were using AI and not use or what how they were thinking about using AI or not at wire speed, and whether they were considering themselves an AI company.
00:16:29.120 --> 00:16:35.440
And um, he had some some good thoughts on that around how AI can produce maybe different results.
00:16:35.519 --> 00:16:42.320
So if you want something consistent, that might need to be at the tool level, and then he's the one who brought up the speed comment as well.
00:16:42.720 --> 00:16:43.440
Yes, yeah.
00:16:43.600 --> 00:16:46.639
Shout out to Jake and Tim over at WireSpeed.
00:16:47.200 --> 00:16:50.799
So uh you get a little bit more exposure to this than I do.
00:16:50.879 --> 00:16:58.320
I'm not in the reports, I think, as much as you are, but from a gaps and vulnerabilities perspective, what are you seeing?
00:16:58.399 --> 00:17:02.559
Are you seeing any kind of common gaps or common vulnerabilities across the board?
00:17:02.960 --> 00:17:10.240
I think we're still seeing people catch up on Active Directory Security because that's that's a big one.
00:17:10.400 --> 00:17:19.759
Um, and then externally, still seeing um vulnerabilities that scanners can't find, though this is getting better.
00:17:19.920 --> 00:17:59.119
I think that's one thing that AI is improving a lot um is application level scanning at scale, because uh your typical network vulnerability scanners won't find something like uh teleric UI is an easy example of just underlying technology in the application that could have a vulnerability associated with it, um, if using the wrong version or etc., where some of the AI-driven application scanners um are able to drive better results there at scale.
00:17:59.599 --> 00:18:19.599
But historically, we're still seeing uh a lot of vulnerabilities come out of that angle of if a network vulnerability scanner can't find it and then it's at the application level, then uh there may be still uh exploits present there.
00:18:20.000 --> 00:18:20.319
Yep.
00:18:20.640 --> 00:18:22.160
Yep, that makes sense.
00:18:22.880 --> 00:18:26.640
So you had mentioned TFTP kind of prior.
00:18:26.799 --> 00:18:31.519
I always feel like that one's kind of underrepresented and not talked about as much.
00:18:31.759 --> 00:18:43.920
I mean, there's a handful of blog posts I've seen in the last couple of years here that call it out, but do you feel like that or any other topics are kind of underrepresented or people aren't talking about enough?
00:18:45.039 --> 00:18:56.880
Yeah, I think um probably that one with uh just SECM and deployment servers being set up in networks in general.
00:18:57.119 --> 00:19:04.319
I think we've given Active Directory a lot of attention and maybe had too much focus on that.
00:19:04.880 --> 00:19:35.519
Um I think the talks that have kind kind of not gotten enough focus at conferences, for example, and things like that is some of the Linux uh environment and like Kubernetes stuff, um where people there's critical infrastructure being hosted there and uh a lot of times um gets missed in common security assessments because there's so much of a focus on Active Directory and things like that.
00:19:35.839 --> 00:19:42.319
Um and then the final one is uh supply chain risks and uh things of that nature.
00:19:42.640 --> 00:19:49.200
Yeah, I feel like supply chain is picking up a little bit because we've seen some of the major compromises happen in the last year or so.
00:19:49.359 --> 00:19:52.720
Uh would definitely that happens every few years.
00:19:53.119 --> 00:19:53.759
Yeah.
00:19:54.319 --> 00:19:56.160
And it seems a little bit more frequent.
00:19:56.240 --> 00:20:07.039
It seems like some of the threat actor groups have been specifically targeting specific repos that they can potentially take over and seeing some of the uh GitHub actions take over kind of things recently.
00:20:07.200 --> 00:20:11.119
Uh a lot of that is getting really interesting to kind of see.
00:20:11.279 --> 00:20:19.279
So I think that's picking up a little bit, but from a Kubernetes perspective, I feel like that was the hot thing, probably like five years ago.
00:20:19.440 --> 00:20:20.799
People are really starting to get into that.
00:20:20.880 --> 00:20:24.799
It not just from an adoption perspective, but also from a security perspective.
00:20:24.960 --> 00:20:29.599
I feel like that's kind of cooled off a little bit, but I think it's really underrepresented myself.
00:20:29.759 --> 00:20:30.480
Uh yeah.
00:20:30.640 --> 00:20:31.839
Because it's definitely out there.
00:20:31.920 --> 00:20:33.599
We run into it a lot.
00:20:33.920 --> 00:20:41.599
But you know, I don't know if it's just we figured out the basics and everybody's talked about it already, and nobody wants to touch it anymore, or or what the deal is.
00:20:41.759 --> 00:20:55.119
But so speaking of kind of hot topic things or things that are kind of fun, do you have a most memorable engagement or favorite exploit that you can talk
about without sharing too much you know info?
00:20:55.519 --> 00:20:56.240
There's a few.
00:20:56.319 --> 00:21:05.759
I think most I'll I'll cop out in the probably most pen testers' most memorable engagement is a successful physical test.
00:21:06.240 --> 00:21:10.559
Um where I was able to get into a data center.
00:21:10.640 --> 00:21:24.319
I found a door that was uh basically broken and could stick my credit card in between the hinge and was able to get in pretty simply that way.
00:21:24.640 --> 00:21:29.359
But um yeah, being able to kind of sneak around a building.
00:21:29.599 --> 00:21:44.799
I was in the break room looking at uh the uh fire escape plan and the building plan so that I could know where to go and things like that, and going around not being asked questions, those are always those are always a fun one.
00:21:45.200 --> 00:21:47.839
Those are really pro tips right there.
00:21:48.000 --> 00:21:50.640
The fire escape plan to get the building map.
00:21:51.200 --> 00:21:59.359
I I don't hear a lot of folks talking about that, but I have personally used that in the past to kind of like map out the different areas I need to get to, and it's super handy.
00:22:00.240 --> 00:22:00.559
Sure.
00:22:01.279 --> 00:22:36.319
Yeah, and then another one, um not sure how much I can talk about it, but it was just a really interesting engagement where um a company was being pressured by a researcher about something the researcher had found, and we were able to work with the developers and really uh assess it end to end and um prove the researcher wrong, but also it was just a very interesting process of really going under the hood of a product and uh testing it end-to-end for this and other things.
00:22:36.960 --> 00:22:38.079
That is really interesting.
00:22:38.319 --> 00:22:40.720
We'll have to talk about that one offline with a little bit more detail.
00:22:40.799 --> 00:22:42.559
I'm I'm curious about that one.
00:22:44.480 --> 00:22:52.160
Uh yeah, we we've had clients come to us uh saying, hey, this researcher is telling us we're vulnerable to this thing.
00:22:52.400 --> 00:22:53.359
Can you confirm it?
00:22:53.440 --> 00:23:00.559
And I can think of probably two or three different situations where we've gone in, either gone, yeah, no, they're actually correct here.
00:23:00.640 --> 00:23:09.680
Uh, here's what you need to do to remediate that, or a couple of situations where this is a really niche thing and it's not really a vulnerability.
00:23:09.839 --> 00:23:16.079
They're just kind of trying to scare you into you know buying their services, kind of ambulance chasing kind of behavior.
00:23:16.240 --> 00:23:19.279
Uh yeah, I'm not a big fan of that myself.
00:23:19.440 --> 00:23:21.839
Uh I think that's not the right way to go about it.
00:23:22.000 --> 00:23:23.359
But always a fun time.
00:23:23.839 --> 00:23:32.640
Now that I know that you're on social engineering, uh, Patrick Saylor, who we had in an earlier episode here, we're gonna have to give him a heads up that you know you might be an available resource here.
00:23:32.720 --> 00:23:34.960
I I didn't realize you had done that before.
00:23:35.839 --> 00:23:48.400
Uh yeah, I haven't done it at NetSpy, but uh I have done it before that and red teaming I kind of stepped away from when I came to NetSpy.
00:23:48.720 --> 00:23:53.920
So I'm curious, did you volunteer to do the social engineering or did you just kind of get booked on it?
00:23:54.480 --> 00:23:55.519
Yes and no.
00:23:55.680 --> 00:24:11.359
Um I so uh so the my previous firm didn't have um our services segmented as much, um, if that makes sense.
00:24:11.599 --> 00:24:18.640
So um I kind of just did the gamut of all things uh pen testing.
00:24:19.039 --> 00:24:20.319
I think that's super common.
00:24:20.400 --> 00:24:37.519
Uh you know, having worked at other firms prior to Nets by myself, I feel like anybody that's you know been at other firms or just in security in general and ended up doing social engineering, a lot of them just kind of got thrown on the project or kind of got voluntoled to do it.
00:24:37.759 --> 00:24:39.359
That's how it kind of started with me.
00:24:39.440 --> 00:24:42.720
It was like, I don't know, Carl seems kind of interested in this.
00:24:42.880 --> 00:24:44.480
Uh let's put him on the project.
00:24:44.640 --> 00:24:52.000
And then you just kind of fly by the seat, fly by the seat of your pants and learn it, and uh it's a ride.
00:24:52.160 --> 00:25:05.279
Uh yeah, I think I think that probably started by when we were very early on in the industry, social and the phishing was usually maybe part of the external pen test.
00:25:06.000 --> 00:25:22.400
But then as the industry progressed, people started getting their phish from other vendors like security training vendors, things like that, um, where they didn't necessarily need it included in the external pen test and things like that.
00:25:22.720 --> 00:25:26.799
Um, so that might have been a shift that played into it.
00:25:27.119 --> 00:25:46.559
But uh yeah, we had at my previous firm we had kind of similar separation, but not um as detailed where we had application and infrastructure, but um the verticals weren't as defined um until shortly before I departed the company.
00:25:46.880 --> 00:25:55.599
Yeah, I think uh when I started here at NetSpy, Scott Sutherland uh was doing a lot of our social engineering and kind of went, Oh, you've done this before.
00:25:55.839 --> 00:25:57.599
Okay, you can do some of it.
00:25:57.839 --> 00:26:03.440
And I I ran with it for a few years, and then we had Patrick join us, and Patrick took it over from there.
00:26:03.599 --> 00:26:16.799
And thankfully we've we've got a much more robust program and uh a lot more training around it uh than I, you know, years ago when folks were just kind of thrown on the projects and kind of well, let's let's figure it out.
00:26:16.960 --> 00:26:17.839
So right.
00:26:18.240 -->
00:26:24.319
Yeah, I think when I started, Scott was leading five services still, I want to guess.
00:26:24.480 --> 00:26:25.599
Something like that.
00:26:25.839 --> 00:26:29.279
But I think we've we've grown significantly in that time.
00:26:29.440 --> 00:26:30.480
So yeah.
00:26:31.119 --> 00:26:31.519
Yeah.
00:26:31.839 --> 00:26:32.559
Well, cool.
00:26:32.720 --> 00:26:44.079
Well, to kind of wrap up our conversation here, we usually like to do more kind of personal conversation stuff, learn a little bit more about you as a person, you know, stuff you like.
00:26:44.240 --> 00:26:53.759
Uh, do you have a favorite hacker book, movie, TV show, any kind of I don't know, media thing that depicts hackers or cybersecurity?
00:26:54.160 --> 00:26:55.759
Uh few, I guess.
00:26:55.839 --> 00:26:56.559
Uh Mr.
00:26:56.720 --> 00:27:07.359
Robot is definitely the most accurate, I would say, just because they got the they had consultants with making sure they were not misspeaking and things like that.
00:27:07.519 --> 00:27:11.920
I thought that was pretty cool that they put more effort into accuracy there.
00:27:12.480 --> 00:27:29.119
Um but I mean the classic, I think my favorite is probably War Games, and then um the movie that actually, as corny as it is, the movie that got me into the idea of hacking was um hackers.
00:27:29.920 --> 00:27:30.240
Okay.
00:27:32.000 --> 00:27:41.680
I was watching it and we had a family friend over that um their son worked in the Navy and information warfare.
00:27:42.480 --> 00:28:04.000
And she was saying that her son basically was a professional hacker, and that caught my ear and started looking into it, and I got in contact with him, and that's basically the real, I guess, start start to getting interested in this and in my journey, I guess.
00:28:04.400 --> 00:28:05.279
That's awesome.
00:28:05.519 --> 00:28:20.319
I feel like it's so more so much more commonplace nowadays for people to know what cybersecurity is, and you know, professional hacker is an actual job title, but 15, 20 years ago it did not seem as commonplace.
00:28:20.480 --> 00:28:33.839
And even in you know, computer science programs, stuff like that, it was kind of talked about like, well, you know, security is important, you should do security, but it never really talked about like consulting or uh you know doing security reviews, that kind of stuff.
00:28:33.920 --> 00:28:39.440
It was just like, well, you know, you should make sure that you protect against these hacker things that you might need to worry about.
00:28:40.160 --> 00:28:41.680
Yeah, exactly.
00:28:42.240 --> 00:28:44.480
I'm totally with you on uh Mr.
00:28:44.640 --> 00:28:45.279
Robot.
00:28:45.519 --> 00:28:49.599
It was so refreshing to watch that and see things be accurate.
00:28:49.839 --> 00:28:54.160
Because I I came into it thinking, uh maybe they'll get it right.
00:28:54.319 --> 00:29:00.319
And then you're watching actual command line terminal things go in, and you're like, yeah, no, that's actually that's the command I would run.
00:29:00.559 --> 00:29:04.240
Who did a lot better than uh two people one keyboard?
00:29:04.720 --> 00:29:05.680
Right, right.
00:29:07.119 --> 00:29:12.400
Or enhance, like yeah, we've we turned a or there was uh what was it?
00:29:12.559 --> 00:29:20.640
CSI said uh see if I can build something and visual build a GUI and visual basic to track an IP address.
00:29:21.200 --> 00:29:21.920
Yep, yep.
00:29:22.079 --> 00:29:23.119
I think that was a good one.
00:29:23.440 --> 00:29:24.400
Yeah, nope.
00:29:24.559 --> 00:29:26.640
So yes, I'm 100% with you.
00:29:26.799 --> 00:29:32.160
Uh very refreshing when it's something that's actually technically accurate.
00:29:32.640 --> 00:29:32.880
Sure.
00:29:33.359 --> 00:29:38.640
I mentioned it kind of at the start here, but you and I met quite a long time ago, I believe at DerbyCon.
00:29:39.359 --> 00:29:40.160
Yeah, yeah.
00:29:40.799 --> 00:29:43.279
So do you have a favorite hacker con?
00:29:43.440 --> 00:29:45.119
And now that DerbyCon's gone.
00:29:45.440 --> 00:29:47.359
Yeah, I mean, dating myself here.
00:29:47.440 --> 00:29:50.000
I think DerbyCon was my favorite, to be honest.
00:29:50.079 --> 00:29:52.720
Um, I was disappointed to see that that stop.
00:29:53.599 --> 00:29:54.880
Um, but I get it.
00:29:54.960 --> 00:29:57.440
Running a con is a lot of effort, a lot of work.
00:29:57.599 --> 00:30:01.039
Um so really appreciate the people that did run it.
00:30:01.440 --> 00:30:05.119
Um, but yeah, I I guess I'd have to default to DEF CON.
00:30:05.279 --> 00:30:07.200
Uh ShmooCon is pretty good.
00:30:07.440 --> 00:30:08.880
Uh I don't know if that's still going.
00:30:08.960 --> 00:30:09.759
I haven't gone into the code.
00:30:10.000 --> 00:30:11.200
That's done now, too.
00:30:11.519 --> 00:30:12.319
Uh no.
00:30:12.559 --> 00:30:12.880
Yeah.
00:30:13.119 --> 00:30:16.000
Um well yeah, I guess I have to default to DEF CON.
00:30:16.240 --> 00:30:22.640
Uh ShmooCon always had a few sleepers, a few really, really good talks that you weren't expecting.
00:30:23.359 --> 00:30:25.119
Um but yeah.
00:30:25.599 --> 00:30:29.440
And that one also had a really good lobbycon presence as well.
00:30:29.680 --> 00:30:30.559
Oh yeah.
00:30:30.799 --> 00:30:31.119
Oh yeah.
00:30:31.359 --> 00:30:34.559
And that was one of the perks of Derby as well.
00:30:34.960 --> 00:30:42.960
Like I said, that's where we met initially, and like the number of folks I met or conversations that we had, you know, down in the lobby kind of area.
00:30:43.039 --> 00:30:52.240
Uh, not that it was better than the talk content, but definitely got tons of value out of that, in addition to like really solid talks that were happening there as well.
00:30:52.559 --> 00:30:53.039
Right.
00:30:53.359 --> 00:30:53.920
But that's it.
00:30:54.559 --> 00:30:55.920
DEF CON's still really good.
00:30:56.000 --> 00:31:08.559
Yeah, I really like all of the
different villages and kind of like subgroups that you get with DEF CON now as compared to 10, 15 years ago, when it was really more like focused on the individual tracks that you had.
00:31:09.200 --> 00:31:22.400
But uh yeah, I usually try to pop into just random talks, just go into a track and sit down and just you know, do the uh the roulette there, and like, well, this one landed, this one's a solid talk.
00:31:22.559 --> 00:31:24.079
I'm really glad I did this one.
00:31:24.480 --> 00:31:25.359
Yeah, yeah.
00:31:25.440 --> 00:31:30.640
I'm also a big foodie, so I have a soft spot for Vegas and the food that is available to you when you're there.
00:31:30.799 --> 00:31:34.000
It's expensive, but yes, offer great options.
00:31:35.920 --> 00:31:43.680
I uh I wish the uh the prices there haven't scaled as high as they have.
00:31:43.839 --> 00:31:47.599
It's extremely expensive now compared to years ago.
00:31:47.759 --> 00:31:51.599
But yeah, you just go put it all on black and see if you're going to dinner tonight.
00:31:51.839 --> 00:31:52.799
There you go.
00:31:55.200 --> 00:31:58.079
Well uh last question here.
00:31:58.160 --> 00:32:08.400
I always like to ask folks about kind of personal projects and you know things that they might be working on outside of work that might be kind of hacker adjacent or kind of home lab kind of things.
00:32:08.480 --> 00:32:14.079
Do you have any personal project kind of stuff that you're proud of or that you're working on that is kind of fun?
00:32:14.880 --> 00:32:21.759
Yeah, I've I'm slowly, very slowly but surely setting up uh a home AI lab.
00:32:22.400 --> 00:32:26.799
I've always run small lab in my in my house, like a few VMs.
00:32:26.880 --> 00:32:30.720
I have a Synology and I run a GitLab server, things like that.
00:32:31.119 --> 00:32:34.880
Um but yeah, slowly but surely setting up an AI lab.
00:32:34.960 --> 00:32:44.160
Um I jumped on the Mac Mini bandwagon, but the problem is the shipping time on those right now is 16 to 18 weeks.
00:32:44.480 --> 00:32:45.119
Oof.
00:32:45.440 --> 00:32:48.960
Yeah, and I think they're coming out with a new one, but I don't know.
00:32:49.039 --> 00:33:02.880
I never thought I would say an Apple product was the most affordable and practical option for a project, but it seems to be with the way GPUs are going and uh servers and things like that.
00:33:03.920 --> 00:33:07.839
Yeah, I've looked into some of the automation stuff around that and and setting that up at all.
00:33:08.079 --> 00:33:10.640
I just haven't had the time or bandwidth to do so.
00:33:10.799 --> 00:33:27.119
Uh, I already have a backlog of home automation stuff with the existing tech that I have and thought about oh well, I could automate it to do this, and like, yeah, but I also need to like fix the 10 other things that I need to do before I actually get to that point.
00:33:27.599 --> 00:33:27.920
Yeah.
00:33:28.400 --> 00:33:29.279
One of these days I'll get it.
00:33:31.279 --> 00:33:32.559
Yada yada yada.
00:33:32.640 --> 00:33:33.440
But oh yeah.
00:33:33.519 --> 00:33:37.039
I you're you're talking to somebody who needs to pull some cat five over here.
00:33:37.200 --> 00:33:37.920
So yep.
00:33:38.079 --> 00:33:39.839
Or well, I guess cat six, whatever.
00:33:40.000 --> 00:33:44.799
Anyways, I need to pull some networking wire at my house that's on the to-do list.
00:33:45.119 --> 00:33:46.640
So well, yeah.
00:33:47.119 --> 00:33:48.319
Ever growing list.
00:33:49.039 --> 00:33:55.359
Really appreciate the time today and getting to uh have a more in-depth conversation with you here in this format.
00:33:55.599 --> 00:34:00.640
Uh, if people want to get a hold of you, any any preferred channels for that?
00:34:01.519 --> 00:34:09.280
Um, I don't keep up with X or Twitter as much anymore, but uh can reach out to me on LinkedIn if you're trying to connect.
00:34:09.360 --> 00:34:12.159
Uh, I keep up with that pretty frequently these days.
00:34:12.559 --> 00:34:13.360
Good to hear.
00:34:13.519 --> 00:34:18.400
And there's typically comments on uh videos related to our release for this.
00:34:18.480 --> 00:34:21.519
So if folks have any questions, feel free to drop those in the comments.
00:34:21.599 --> 00:34:25.360
We try to keep tabs on those, see if anybody has any questions we can answer.
00:34:25.599 --> 00:34:28.559
But uh yeah, really appreciate having you on today.
00:34:28.639 --> 00:34:32.159
And anything else that you might want to promote or share?
00:34:33.119 --> 00:34:34.800
Uh nothing more from me.
00:34:35.199 --> 00:34:35.760
All right.
00:34:35.920 --> 00:34:39.440
Well, again, thanks for the time, and we'll talk to you later.
00:34:39.840 --> 00:34:40.719
Thanks.
00:34:40.960 --> 00:34:43.280
And that was our conversation with James Albany.
00:34:43.440 --> 00:34:45.920
Thanks for joining us on this episode of Hack Responsibly.
00:34:46.000 --> 00:34:52.239
If you'd like more episodes, make sure that you like, subscribe, follow all the things, and check out NetSpy's website to get connected with us.
00:34:52.400 --> 00:34:52.880
Thanks again.
00:34:53.119 --> 00:34:55.039
Remember, Hack Responsibly.