Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

CYBR.SEC.CAST

CYBR.SEC.CAST artwork

Definitions of Pen Testing with Darin Fredde

Apr 2, 202536 minAudio
  • Apple Podcasts
ShareXLinkedInFacebookWhatsAppEmail

Sam and Michael are joined by Offensive Security Advisor, Darin Fredde! They discuss the need to move beyond compliance checkboxes, the importance of continuous pen testing, and the disconnect between marketing claims and real-world security implementations. Things Mentioned: Having trouble with your OT.SEC.CON. or EXEC.SEC.CON. ticket? Reach out to us at info@houstonseccon.com Expired Domains Allowed Control Over 4,000 Backdoors on Compromised Systems - https://thehackernews.com/2025/01/expired-domains-allowed-control-over.html Watch Darin’s Talk: https://youtu.be/SAW0qdTgcWY?si=Z_Dc-gNWcPtjdVgi Do you have a question for the hosts? Reach out to us at podcast@houstonseccon.com Keep up with HOU.SEC.CON.: · LinkedIn · Twitter · Facebook · Instagram · YouTube · Bluesky Check out our other show: · CyberSunday Check out our Conferences and Events: · HOU.SEC.CON. · OT.SEC.CON. · EXEC.SEC.CON. · HSC User Group Support or apply to our Scholarship Program: · TAB Cyber Foundation In this episode: · Host: Michael Farnum · Host: Sam Van Ryder · Guest: Darin Fredde · Production and editing: Lauren Andrus · Music by: August Honey

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_03And welcome everybody to HusekCast, the HusekCon podcast. How are you doing, Sam? I am hunky Dory. How are you doing, Michael? I'm good. I'm uh trying to stay warm while we're recording this. It's tad bit chilly for Houston.

SPEAKER_02For us poor Houstonians that are suffering at 58-degree weather, right? Yeah, it's horrible. It's horrible.

SPEAKER_03That's why I got my jacket on. I got that extra blanket at night, and my old bones can't handle it. Uh well, I'm excited to have Darren Freddy on. Darren is the uh cybersecurity manager at Stratus, and he's been doing a lot of uh pen testing stuff for quite a while. His talk at HUSECCON was all about markitecture versus actual security and how you do continuous penetration testing to uh to make sure that the tools you put in actually do what the marketing guy said that they do.

SPEAKER_03So kind of a big deal.

SPEAKER_02Kind of a big deal. Yeah, definitely kind of a big deal. Yeah.

SPEAKER_03So he's he's got some good use cases. Uh, so I'm excited to talk to him. So let's get to it. Let's go. And Sam, we're here with, like I say, always say a special guest, but I'm excited to have him have him on. Darren Freddie, how you doing, Darren?

SPEAKER_01Hey, Michael, thank you. Thank you for having me.

SPEAKER_03Yeah, glad to have you. So Darren is the cybersecurity manager at Stratus, and he's gonna be going over his talk today. Sam, I know you're excited about this talk, right? Totes. Totes McCotes. Yeah, no, Sam. Uh, we we joke about stuff where uh Sam's Sam. Small words. Small words, yeah. Like I'm not technical. Very slowly. Sam, a lot of people don't know that Sam was uh comes with an engineering background. He's he's a lot smarter than he lets himself out to be.

SPEAKER_03He just wants to play the dumb sales guy sometimes, but he's smart, dude. Because it's so beneficial. People don't realize. I mean, don't don't put that out there, people are gonna know. Oh man, yeah, it's gonna mess his mess his game up. It's gonna mess his game up. Well, he used to be my sales guy, and I I picked up on pretty quick, but that's okay. Well, seriously, uh, Darren, glad to have you on here. Uh, we're gonna talk about you in just a little bit, but before we do that, we've got to talk about USECCon.

SPEAKER_03Sam, you've got the first one here. This is your baby. What's going on with OtsetCon?

SPEAKER_02Yeah, so we've got that coming up on April 4 uh 17th, and uh sponsorships are all sold out. So uh appreciate all the sponsors that have stepped up to do that. Um, we will expand for those that did not get there this year. We will have more opportunities for sponsorships next year. So keep it on your calendar. Sold about a third of the tickets, they are going fast. So the ticket sales are picking up. That's awesome. So be sure to go get. We will sell out again. So please go get your ticket now. Uh it is a new ticket platform and it's a two-step process. So once you register or once you apply, you'll get approved.

SPEAKER_02And then you got to go back and get your ticket. And if you have any issues, just send a note to info at HoustonSeccon.com. Um, and then we'll uh we'll we'll get back to you. This is also just to be clear on attendance, like we are really focused on the owner operators. So we're looking for folks from whether you're uh in the cyber side on the IT side of things and you're in an owner operator, you know, whether you in a SOC or a CISO or whatever, or if you're out in the field, if you're IT in a plant or uh you you have purview over uh as an engineer over any of these systems, then we want you there because we want to try to get this uh discussion going and everybody collaborating together.

SPEAKER_02So uh just know that as we're going through the uh if you will, the approval process, uh, those are the folks that we are letting in at this point. Uh hopefully we'll be able to expand that next year. Yep. And then after that, the week later, what do we have for the week later?

SPEAKER_03We've got ExecSecCon. So ExecCon, as everybody hopefully knows, if you listen or if you don't, uh, that is our uh version of an executive level cybersecurity conference. Um, we've got about a third of our tickets sold there. That's on April 22nd. It's always, you know, a little bit smaller. Uh executives are busy as well. So they, you know, they need to get out there. But we we sold out last year. We're gonna do that again. So please go register. Um, it is execsetcon. That doesn't mean you have to be an executive. You don't have to be a C Sodian there.

SPEAKER_03If you're managing director or a manager or somebody who's trying to move up into those ranks, uh please, please come out and register for it. Again, also a two-step process. If you have registered for that, same thing. And if you haven't heard back, uh, that's that two-step process. You should be getting another email. So if you haven't seen that or if you're having problems with it, again, send out to info at Houstonsetcon.com and uh we'll be able to get you uh some help there and get you to that next step.

SPEAKER_03Again, any anyone in a leadership role, um, directors, deputies, VPs, presidents, that kind of stuff. So get out there and do that. Uh, we're we're really excited about putting that together as well. And then uh what's next?

SPEAKER_02UseCon, Sam. The big one. That's gonna be September 30th and October 1st at the George R. Brown. So tickets are open, sponsorships, uh, so you can go get your ticket now. Be mindful, we are staging the ticket prices. So the longer you wait, the more expensive they will get. So go get your tickets early and don't wait. Um, we also have a lot of sponsorships still available. So uh that's starting to heat up too. We're getting a lot of those uh um contracts in. So if you're in the space and you want to meet a lot of awesome people in the space and uh come come out and sponsor QSICCON, we'll have the call for papers out the entire month of May.

SPEAKER_02So put that on your calendar. If you want to come talk, uh, we want to hear you. And so that application process will between May 1st and May 31st. And then we have a really cool initiative uh actually uh coming up that we've been talking about for a while. That uh we have some very smart people leading for uh youths at con. So uh we've often talked about this. This is a community building event at our our conference, and and part of that is building the next phase of community. So bringing in those uh high school students is what we're gonna be doing this time. So when you're at the um we're looking for uh kids in the ninth to twelfth grade that are interested in cyber or considering it and we want to see them there, there's a process for going through that as well and give them the experience uh of the cyber world.

SPEAKER_02Like let's sit, let's have them part of our community and and experience what a great family we have here. So very, very excited on that. And the space is limited. So uh be sure to get ahead of that if you can too.

SPEAKER_03Yeah, the space is limited. Um, if if you've got a student that wants to go and they want to go on their own, the tickets are free to them. But if they're not with their school, then the guardian needs to also be attending HughesetCon, being staying there, that kind of thing. There's some various rules that we've got set up. I won't dig all into the weeds, but just know that we're inviting some groups of like schools to bring groups or individuals, but just make sure you go through it. If you've got any questions, you can also hit us up on that info at HoustonSetcon.com link.

SPEAKER_03All right, let's talk about the latest news stuff. So we've got an article here, which Darren, I thought you would appreciate. Uh, it's all about how some uh expired domains out there um from attackers let other attackers get a hold of them and also let security researchers who are trying to stop those attackers from uh doing bad things with those domains, they took them over. So the reason I thought it was funny is just I I think we've all said this.

SPEAKER_03Anybody who's involved in any kind of pen testing or third research or anything over the years has said that the bad guys are often just as bad or worse than we are at things like opsec or just basic security functionality or IT function, you know, any of the operations, processes, procedures, that kind of thing. Um, and this one's all about some uh bad guys leaving a bunch of back doors or a bunch of systems open, a bunch of uh expired shells.

SPEAKER_03Yeah, shell, yeah, a bunch of shells sitting out there. They got like over 4,000 backdoors that are just sitting out there, and they just haven't done anything with them. They've sat there and they got it expired, and now you got a bunch of researchers out there grabbing them. Uh, this one was specifically Watchtower Labs. Um, they registered over what 40 domains that had backdoors. There were designed to build out their command and control infrastructure. Um, they said they were in partnership with Shadow Server Foundation. Um, so they had probably sinkhold a lot of these domains.

SPEAKER_03Uh it was just, I just thought it was interesting, nothing like crazy fantastical or anything, but just thought it was funny. So, what what do you what's you ask your take on it, Darren?

SPEAKER_01Well, I the the thing I like the most about his creativity. Yeah, if you notice the um and catching people in their blind spots, that's the one thing that always really inspired me about pen testing is how to take conventional wisdom, you know, the way that we think we understand something, and then all of a sudden you you come at it at this angle nobody expects. And I like the way the researchers did that. They probably had that in mind for a while and they were ready to pounce. And then once that came open to them and they knew that it was something the attackers kind of let's call it, eat off the enemy, you know.

SPEAKER_01Uh the enemy had kind of made a mistake, they executed. And and it kind of has a double. What I like about it, it has a positive part of it too, is that they did it in an ethical way to take those off the market. At the same time, they're uh doing the community a good service by making them aware of it. And more, but I'll I'll kind of wait for you to ask me more questions about it. But I I I loved it. I I kind of sat there and read it over and over again, and that's the stuff I live for.

SPEAKER_02I thought it was uh for for me, uh it went a totally different route. I'm looking at that going, I'm already paranoid losing my own domain. So uh I've got a reminder, you know, that tells me to go renew every five years or what I do, always do the maximum, right? So I don't lose it. But then I'm also thinking, I'm gonna forget about this with so many years. So come, you know, January 30 and 30 or 2032, I'll have to renew again or whatever it is. And so I have my reminder, but I I thought it was funny to have all that stuff because I know another guy that registers domain after domain after domain constantly.

SPEAKER_02And I don't know how you keep up with that, Michael.

SPEAKER_03So uh well, it's it's called turn on auto renew and uh have it reminded you so I don't have to remember some of that stuff, but yeah.

SPEAKER_01Yeah, I I I do a lot of things when I come into infrastructure, whether I'm approaching it from a blue teamer standpoint or or just curious. I always look at people's attack service like that for any subdomain takeovers and things like that, because I know that the enemy does that, you know, they spend a great deal of time of trying to work those angles. You know, one I was going to tell you, throw you a little curveball here, Sam. One thing that caught my attention is I, you know, part of the talk that we'll get into later, you know, was I was talking about um architecture, which I won't get into.

SPEAKER_01We'll talk about that later. But that talk was about one thing I said was not allowing the pen tester to do the full life cycle. And when people don't really understand offensive services and testing, they may turn it into a red team exercise, cut the pen tester off. He can't finish his full life cycle, therefore he can't clean up properly, you know, and that can occur, has occurred to me before where people have misunderstood testing. And then the other thing is that they turn it into a red team exercise when it's really a pen test.

SPEAKER_01And we'll we'll get into more of that later. But those were a couple of things from my experience that pointed out is like, oh yeah, I've seen that happen where I had to look beg the guys, hey, listen, you don't understand. I was right in the middle of a POC. You need to ensure you clean that server up, you know, because that typically happens at the very end and post-exploitation, all these things that we're talking about that were taught in PTES, you know, it happens later on in the um life cycle if you're doing that type of testing. If you're doing compliance-based testing, it can be missed.

SPEAKER_01So that's part of the reason why I developed the talk.

SPEAKER_03Yeah, if they're not going in there and cleaning some of this stuff up and you know they're in the middle of it, it it does make me wonder how many times they got maybe interrupted in their attacks when they were trying to, you know, put the whole thing together and somebody got in the way. Or I mean, who knows? I mean, that could have just been a could have been another gang. I mean, I remember Sam and I uh both had the same customer and they had a gang in their environment, constantly sitting in their environment, had just was they couldn't get out of them, they had uh total control of the environment.

SPEAKER_03And we were like, Well, you need to get some of this cleaned up, you need to do this, you need to do that. And they were like, Well, you understand, we've got another gang that goes and cleans up their stuff for us, and then comes in and puts their own persistence in place, and then that other gang comes back. So we're like, we kind of just let them do because they're so busy cleaning each other's stuff and trying to take their persistence away that we don't have to do anything. And I was just like, okay, if that's the way you want to think about it, but it it just I thought it was pretty interesting.

SPEAKER_02The time the two muggers try to fight over your wallet, right? So yeah, just silently slide out.

SPEAKER_01Well, I think there's a lot to say. Um, there's a lot of attack vectors that are risks or hidden risks that set behind post-exploitation, right in between what we'd call a red team exercise versus a pen test. And if you're doing compliance-based pen tests, like I said, and you you know, the group has a different understanding of the pen testing, you don't get to complete and find all those attack paths, which continuous pen testing does nowadays, you know, you miss some of those. So those were kind of some interesting things I found, you know, from an offensive standpoint, plus the need to do continuous pen testing.

SPEAKER_01It's just uh another evidence that you know, a snapshot in time is just not good enough anymore. Yep.

SPEAKER_03We're gonna dig into that. And uh when we talk about your talk, very much so. So thanks for uh the all the comments on this. And on the other side of the break, we will uh we will dig into all things about Darren and then get into his talk. So enjoy the break. We'll see you in just a second. And we are back. So, Darren, this is the part of the show where we talk about you, and we want to spend the first few minutes like we always do, uh getting an idea of what got you into pen testing, into this whole space in general.

SPEAKER_03I know you and Phil have known each other a long time. I don't know how much he was involved in that story. He's obviously a friend of the show and a friend of the conference as well. Um, so want to get your get your rundown, man. What what got you into cyber, what got you into pen testing? Why do you like it? Why do you keep doing it?

SPEAKER_01Well, it gets me out of bed in the morning. I I personally believe that I um I've kind of gambled on my whole career on the fact that I believe offensive services and are the way to build models to really understand risk. I think it's the best thing we have today to really understand you know, complicated risk items with impact, but I didn't start that way. I started um I've been about 20 plus years for me. I started originally in telecommunication. I met Philip, you mentioned I'll go ahead and layer him in the story, because he is how I transitioned into pen test.

SPEAKER_01So I met him in 1995. We were both in computer cat operators. He's got a good uh talk if you want to hear about the way I started. So I'll give you the short version, but I started as a C LEC in the I LEC days before browsers are around and everything. And at that time, I really didn't think much of security. I was chasing the IT like everybody. I wrote all that up until I was a CIO for a bulk liquid carrier. And about that time, it was post-September 11th, that's when I really started kind of really getting interested in cybersecurity.

SPEAKER_01So I kind of retooled at that time. I was still, I went to school at the same time I was um uh a CIO and I had intentions of basically, you know, bridging back in. And so I started out like most people, I guess, what I'm saying is IT. And then um I've since then I've been in, you know, I've held many roles, security architect, security analyst. Um, I've been a security engineer, and I've been a consultant for a company with local governments.

SPEAKER_01I've done pen testing with local governments. I also teach at a university. I teach an ethical pen testing course at Dallas College. Oh, yeah. I've been doing that for about six years. I also um heavily involved in the community. I run uh the North Texas Cybersecurity Group here in Texas. And then how I got into pen testing was I was pretty miserable on the uh architecture side. I was a security architect for a company, and I couldn't, I was having difficulty getting the audience to understand the impact of something.

SPEAKER_01And I was real frustrated with it. And Phil said, uh, hey man, why don't you just come over here and be a pen tester? And at the time he told me, I was like, Man, man, I I I've never done pen testing in my life. How could I do that? And he said, Man, you don't really understand. You would be really good at it. And that's how it all started. I went in to a bank, one of the largest banks in the US. I felt a bit like I needed to keep my mouth shut, you know, for a year. And I did about a year, I watched things, and then I was studying the attacker at the same time, and I just felt like, you know, there's a big difference between what we're doing and what attackers do.

SPEAKER_01And I talked to a couple of the guys that were running the group, and basically what ended up happening, uh, Michael Sam is they turned me loose. They took the cuss off of me and uh basically allowed me to start hacking. And I would start from a Windows box and just start hacking from where I was at. And uh that led into a lot of problems, you know, discoveries within the bank and everything, as you would expect. And this was kind of prior to living off the land was still around, it was still uh very popular, but uh Baz wasn't around at that time, hadn't quite made the scene.

SPEAKER_01And um, so I was going to film, I was like, what do we call this? You know, I mean, because it I can't really call it uh pen testing because you know they're a little longer. I'm not doing red teaming, but yet I am emulating a threat. So we I called it full scope adversary emulation. And I'm sure your viewers are wanting to argue with me right now about definitions of pen testing, but that's what I was saying earlier. Is one thing I noticed about that method is that um it allowed me to do the full life cycle, but it also blurred the lines between traditional pen tests, even though I wasn't being covert.

SPEAKER_01So I did that and then I developed the product out of it uh for a side company, and I did both of them for about six years. And that's where the talk came from from my experience of doing all that.

SPEAKER_03Well, that's that's a good lead into the talk. But I mean, the I think what you talked about before, and Sam and I've had this conversation with a few of our guests, is like some of us that are a little bit long in the tooth. That's kind of where we came from, was that IT background, and then moved into the security architecture background. And I think that, and I think Sam, you would agree that it gets you a lot of experience that it's not a young kids don't know what they're doing these days kind of conversation. It's just we've come up in it in a different way, and we're not entering security kind of from like an analyst perspective.

SPEAKER_02Or so it's good to have, it's good to have the fundamentals, it's good to understand what you're trying to protect to begin with. So I don't think anybody can go into a cyber security position without understanding what they're actually what the uh crown jewels are.

unknownYeah.

SPEAKER_01Yeah, I I agree, Sam. I think it's kind of think like an admin. A lot of people say think like an attacker, but when you're the offense, you know, you're the offense, I'm thinking like the admin. Like, when do you take your breaks? When do you go and deal? Uh, are you trying to find the agent? Is there a guy in the sock that's spending all his time trying to figure out why his agent's falling offline? You know, because that human complacency, the human factor in the misconfiguration of the vulnerabilities are the things I'm looking for. I'm looking for those rare moments that make people go, what?

SPEAKER_01You know, like I like to use this one as an analogy, if you don't mind, Sam. I I at one job I'd use the bus driver's credential. So just saying that out loud, I'll repeat it again. I use the bus driver's credentials. It the ludicracy that a bus driver would have credentials is your first knee jerk reaction. And I used it because of the human factor of making you pause, like what? And then I used that to um not do what you expected me to do. I went after.

SPEAKER_01Sensitive data, you know, straight for the sensitive data. Don't really care if you think I'm elite. You know, I'm I'm I'm there for a mission. And um, I I just always kind of thought that way. And I and my background helps me in that regard.

SPEAKER_03Let's use this as a segue then. Okay. Let's uh let's get into your talk. So uh the talk is uh all about you and you said the word before, it's around markitecture. So marketing height to you know basically line that up against real security validation of the controls. You're doing that through offensive testing. You you said the acronym BAS. I think a lot of people may some people do, some people don't know. That's breach and attack simulation. So, and then you've got the automated PIN testing that you talked about.

SPEAKER_03You kind of built that out and did that a while back before those had kind of started hitting the market um in a in a large way. I think the first one was probably what that most people know about anyway, would be like what Veridin that got bought by uh who they get bought by I think Mandy owns them now. Uh FireEye, Mandy, all that good stuff that's now part of Google Cloud. So I this is a topic that I mean, I've said in the past when I first saw breach and attack simulation tools come out, that kind of thing.

SPEAKER_03I was like, look, if I was a new CISO walking in the door, I would as much as possible stop all new tools getting implemented. And I would put something like this in. And I know there's there's problems getting it implemented. There's always issues getting some of these tools implemented in an environment, but I would put something like this in to validate the controls that I had before I implemented anything else. And I think that's not the full scope of your talk, but I think you would probably agree with that.

SPEAKER_01Yeah, maybe not, maybe not. Um the acronym, but the the intent, yeah, the continuous pen testing. Yeah, I would agree a hundred percent, Michael. Um, and and I had a lot of bumps and mistakes along the way. Uh a couple of times I got accused for hey, you're doing an undisclosed pen test. That's like, what's an undisclosed pen test? You know, just ridiculous stuff. And it it um it just a lot of mistakes I made, you know, like getting caught up in the ego because I was really good at stealing passwords.

SPEAKER_01I mean, I would steal a lot of passwords, and I was real good, but I was embarrassed about it because I was thinking, you know, this is an elite, you know, this isn't me. And but it worked, you know. I I can do credential shuffle and you know, I can really own this environment and take over the doors and you know, and the cameras and just full, you know, full ownage of an environment. And it um it disturbed me that it was uh that I could do that. And then I would, I never was really trying to test the red team, I mean the blue team in those tests, but I would get accused of it a lot, you know, and I'd try to say, okay, I'll tell you what, I'll send you an email every time I start a test.

SPEAKER_01We good with that? And you know, I would do things like that, and I would explain to them, look, if uh if credentials are in my scope and you're, you know, your security compliance device is in configured, you can bet I'm gonna tamper with it. I'm gonna turn it off. I'm gonna jack with your environment and I'm gonna leverage the architecture. And um, it took a wall, you know, to kind of get people to come around, but um, it exposed so many different findings and it created different problems too. One of the bigger problems it created, Michael, was you know, these are not findings, these are projects.

SPEAKER_01I think Phil said that at one time, and and they were because they were gross misconfigurations within the security architecture. So there's where the talk kind of came together.

SPEAKER_03So from the validation, then I mean, it when you're when you're talking about marketing versus reality, what I and and correct me if I'm wrong here, but one of the things I got from your talk was that they, you know, they got the marketing that says it can do this. It may be 100% capable of doing that. But if you, as the architect or whoever that are implementing that tool, don't one turn everything on based on your environment that's key to your environment to stopping attacks, and two, you don't monitor those things and you don't watch them, the validation of those is going to fail because you don't you're not doing what you should do with this tool.

SPEAKER_03It to me, it came down to a little bit of sometimes some laziness on the implementation side of it. Is that is that a fair assessment?

SPEAKER_01Yeah, and the lack of testing. I mean, if you kind of here's what kind of caught me off guard is um, and I don't know I'm right about this, it came from kind of a thesis. I kind of worked backwards, see this problem, and then try to prove myself wrong or right. And one thing I saw is that if you're been around a long time, Sam and guys, you remember we used to have CTOs. So we'd have a CIO and a CTO, they and it was the IT was innovation. Then we got rid of the CTO, so the chief technology offices is gone.

SPEAKER_01And then I noticed this lack of vision for your architecture. It would just build sporadically. And it was, it was if if one could I could argue that you're architecting your security architecture on the back of IT architecture, it's scaffold on it and it's interlaced, right? Layer defense. And I just noticed this lack of vision of where you were going, this overlapping sprawl of tools, and no testing. And nobody would take a product, you know, you wouldn't take a product as a software development company and put it into a customer's environment without testing it, right?

SPEAKER_01So why the hell would you do that with your security architecture? And I noticed that they didn't, when I would Google search, it's very hard to find one person responsible for it. A lot of people will tell you, well, the chief security officer is responsible. Really? For setting the vision and this complex architecture, no offense to chief security, you know, for CISOs, but it and then maybe say the security architecture do it. Well, really, he really is over one area. So then I thought, well, there's really not a role for this.

SPEAKER_01And that's what's allowing me to wiggle in between these systems, is because of this gap, you know, between things and no efficacy testing. And that's when I came up with, you know, thinking, oh, there needs to be continuous pen testing. Now, that wasn't me trying to claim I came up with that for the whole market. I just was kind of in line with their thinking at the same time.

SPEAKER_03Yeah.

SPEAKER_02But this also kind of makes me think about the the situations I've been in where I've I've seen some of the pen testing happen, et cetera, where customers basically have the cutoff point saying don't go any further or um want to want to change the outcome of the verbiage in the in the in the assessment, right, that comes back to them. And some of that I'm sure is CYA. But like what's the point? And I think, you know, if there was one thing that I got that kind of uh gave me a little bit of an aha moment when I was watching your thing, was it not just talking about as a pen test, but as offensive security testing.

SPEAKER_02Right. And that changes for me, that changes the the perspective of what we're doing here, right? It's not just trying to get in somewhere and try to knock things down. It's the it's much more than that. It's it's ensuring, like you're talking about, is finding the right architecture and the things you need to fix, right? Or did I misunderstand that, or is that kind of where you were headed?

SPEAKER_01No, you you know that Sam, um, there's there's a lot of problems with, I personally think, with offensive testing in general, because compliance really helped us out, right? We get a lot of testing done, but there's this need to uh, if you're a person who knows how to do that type of testing full scope, um and you can attack and really own the environment, stopping the attacker before he finishes um can allow, can make you have a false understanding of your security.

SPEAKER_01And that and that, and that's you know, if you're doing snapshots in time, you're not necessarily going to find all those attack paths. So if uh if you get social engineered, somebody drops on your box in a Windows environment and starts moving laterally, you may not see that he can exploit uh software through grammarly. I know that sounds ridiculous, but what if you're locked down and then he goes and he's filtering data? That's a post-exploitation type scenario. But it it so it requires a different type of testing, and that's why I started doing that.

SPEAKER_01I I was actually surprised the market bought it. There was quite a few customers, local governments that and use cases I do in my talk, and all of those bought that product, full scope adversary orientation. That's the way it was pitched, and that's the way they bought it. And and some of them would allow me to really take the gloves off and pen test.

SPEAKER_03So you talk about use cases. Before we close this off, when I was watching your talk, one thing just cracked me up was when you were attacking that uh company, the helicopter company, and y'all were watching videos, and there was this one video on a boat. What can you tell tell us about this because it cracked me up?

SPEAKER_01Okay. Yeah, there was a a buddy of mine because at that time I wanted to create this, I collaborate better. So that's why I like the blue team, red team scenarios, because I like having authentic dialogue, checking your ego at the door and talking about problems, you know, realistically. So I had a friend of mine, and we were doing the test, and the whole test, the thing we want to see is we want to see the the helicopter flying around and all that uh spy stuff, you know, and video. And so it's a good friend of mine.

SPEAKER_01And um, we finally, at the last of the tests, we had gained access to where he owned everything, and we were watching video, having popcorn, watching these people get arrested. And and there was this one boat, and this guy was getting arrested, and my eyes fixated on a dog because I'm a dog lover. I was like, oh, there's a dog on board, and they were arresting him. And as I was like, they're gonna leave the dog, and then sure enough, they arrest him and they just drive off the boat sitting there. So we made this whole skid out of uh they left the dog, you know, or and and that became like the dominant factor.

SPEAKER_01And then uh we had all these jokes and everything about the dog swimming and sharks getting in, and it was cool. Oh my gosh, well, totally it was totally fiction. I'm sure I'm sure the local um you know department went back and got the dog, but uh yeah, that was a pretty cool test. Uh that was uh I can't reveal the client, but I can tell you that it was uh around the United States. And we to be specific, we didn't we didn't do anything, the helicopter, we just did the streams, you know, that you that officers would get.

SPEAKER_02I hear they trained that dog to be a pen tester later on.

SPEAKER_01Yeah, he was resentful. I talked to him, he was really upset. He said, I am a good dog.

SPEAKER_03No, I'm just now give me a milk phone. Yeah, I was watching that, it just cracked me up. So I was all I can think I was like, I hope they got that dog out of there.

SPEAKER_01That's what I got caught up on. I was like, screw the guy get arrested. Go back and get the dog, go get the dog.

SPEAKER_03Well, Darren, I really appreciate it, man. Thanks for going through that again. Thanks for uh supporting UsecCon coming out and talking as well. It was really good to have you have you out. So any uh any parting thoughts?

SPEAKER_01No, I just want to tell you I really appreciate it. Hopefully, that um our discussion has you know uh impressed upon the users, you know, the need for continuous pen testing and then doing it at scale. So I appreciate it. Absolutely, man.

SPEAKER_03Absolutely.

SPEAKER_02Sam, no, I mean uh good, good, good stuff, and I learned a few new things, uh, which is always awesome whenever I can uh go through a presentation, pick up some new stuff, like new cool words like markitecture.

SPEAKER_01It's a port, it's a portmanteau. I had to look that up. So it's not that I'm that clever, it's it's a combination of two words.

SPEAKER_03So yeah, I've I've used that a couple of times in my in my uh career, and people always get a kick out of it, especially when you find that one person who's never heard it before. They're like, oh, that's a cooler. All right, everybody. Well, thank you for joining us with Darren Freddie here, and we will see you soon.

SPEAKER_00This has been a Hugh Setcom production. Hugh Setcast is hosted by Michael Farnum and Sam Van Ryder, with production and editing by Lauren Lynch. Our music is by August Honey. The views and opinions expressed in this show are those of the speakers and do not necessarily reflect the views or positions of any entities they represent. This show is for informational purposes only and does not render or offer to render personalized advice. Subscribe now so you never miss an episode. You can follow us on LinkedIn, Twitter, Facebook, and Instagram at HustetCon, and you can learn more about our events or buy tickets at HoustonSetcon.com.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Asking too Many Questions with Michael Santarcangelo

    Nov 11, 202633 minAudio

    In this episode of CYBR.SEC.CAST, Michael Farnum and Sam Van Ryder sit down with Michael Santarcangelo, founder of ValueSmith, to discuss delivering value that others can actually recognize. With three decades in the...

    • Apple Podcasts

    Credit the people on this episode

  2. Keeping up with the Times with Jody Brazil

    Nov 2, 202630 minAudio

    In this episode of CYBR.SEC.CAST, sponsored by FireMon, Michael Farnum and Sam Van Ryder sit down with Jody Brazil, founder and CEO of FireMon, to explore how AI is reshaping network security and why traditional...

    • Apple Podcasts

    Credit the people on this episode

  3. AI, Risk, and Ewoks with Peyton Kennedy

    Oct 28, 202635 minAudio

    In this episode of CYBR.SEC.CAST, sponsored by Endor Labs, hosts Michael Farnum and Sam Van Ryder sit down with Peyton Kennedy, Senior Security Researcher at Endor Labs, to explore the hidden risks of AI adoption,...

    • Apple Podcasts

    Credit the people on this episode

  4. Not a Finance Guy: Building Companies with Bob Ackerman

    Oct 14, 202634 minAudio

    About this episode: On this week’s episode of CYBR.SEC.CAST, Michael Farnum and Sam Van Ryder sit down with Bob Ackerman, Managing Director at DataTribe, to share lessons from decades of building and investing in...

    • Apple Podcasts

    Credit the people on this episode

  5. The Wild West of Deploying Agents with Nadav Cornberg

    Oct 6, 202634 minAudio

    About this episode: In this episode of CYBR.SEC.CAST, Michael Farnum and Sam Van Ryder sit down with Eve Security founder and CEO Nadav Cornberg to explore the challenges of securing agentic AI. They discuss AI...

    • Apple Podcasts

    Credit the people on this episode