TRANSKRİPT 🔗
WEBVTT
1
00:00:00.000 --> 00:01:24.000
Well, and as I've built out teams in my past and current, even whether it's at, you know, EY or as an asset owner, like early on when I. Again, when I was an asset owner, hiring folks for this OT stuff, OT Word didn't exist and I needed to find people that could fill the roles that I had. So it was really hard to find somebody that had the skill sets that I needed. So I was looking out to skilled, you know, labor type folks because I'm looking for a mindset. You think your network Segmentation is at 80%. The pen test says you're at 10. This week I talked with Orin Miskin and Ronaldo Gonzalez on OT penetration testing, why doing nothing is no longer an option, and how to get people comfortable with going to the cyber dentist. Thank you everybody for joining me on another episode of the PrOTect IT All podcast. This is take two of this episode. We had some technical difficulties, which tends to happen from time to time, which is no problem at all. But I'm very excited to have my friend Oren on on again the podcast. And then Ray, this is your first time. Well, I guess you were on it last time, but we. It didn't get to the end, so we're starting over. So this is technically your first time on the podcast. So, Orin, for those of the audience that doesn't know who you are, why don't you introduce yourself and tell us who you are, how you got in the industry, what you're doing nowadays, like all that kind of fun stuff.
2
00:01:24.000 --> 00:02:25.000
Yeah. And since, since I was on your show last time, now I'm a principal secure OT security engineer. So my kids are very scared of me. They think I'm a principal. I was thinking about making a sign that said or in principal's office, but I haven't yet. But anyway, so I am a principal OT security engineer with GuidePoint Security. I've been in OT for over 20 years, which if you heard me speak ever, I like to say whenever you hear that, you should be a little bit skeptical because OT hasn't really been around 20 years. So. But I was in O before OT, so I was crawling around in the bilges of drilling rigs and Navy ships and just being electrician and electronics mate, electronics technician and then proceeding on to IT and consulting and eventually OT cybersecurity. And once I hit that, I was just like, oh yeah, this is where I need to be. And all the spy versus spy and all the stuff, I got caught up in it all and here I Am I don't think I'll ever leave. So that's my background.
3
00:02:25.000 --> 00:02:27.000
Awesome. Ray, you're at buddy.
4
00:02:27.000 --> 00:06:02.000
Right, Right. So everyone. Yes, My name is Ronaldo Gonzalez. I either go by Ray or Ronaldo. Depends on how you want to pronounce it. But you know, I guess really for, for me the way, the way it started for, you know, for my career or my journey was I actually come from the, from the IT side. You know, I like, like a lot of people I started with the interest in computers when, you know, when you're young,
Load full transcript
building computers, messing them up, trying to fix it. I remember having my first activa model computer where, where we browse, you know, the AOL and got infections for malware, kind of fix that. But what, what really got me into IT is is being able to just kind of explore that kind of technology. And then, and then I was doing kind of like networking courses without building cables, Ethernet cables, when I was in high school, like sophomore. And then from there I we had an opportunity to learn networking. So we took like the Cisco CCNA classes to learn about the routing and switching. And then from that moment I knew, okay, I want to do technology, I want to do network. So I went off to college, got my degree in the networking side, graduated. I got my, my first job at Cisco Systems and I was there for about 13 years doing a lot of the, I did like the network engineering side, did consulting, I was databand services team then. But I got to really support a lot of customers in the us, South America, Central America. And the exposure of being able to see different types of networks and environments was, was an interesting part to seeing how these things, what I learned about in theory class was one thing, but then when you actually apply it to what seeing real customer networks was like, so that's how it makes sense, you know, being able to see that perspective. But the bridge for me in security happened more as throughout my years at Cisco I got more into security related projects like network security, doing more infrastructure architecture. And at that time I was living in Spain and I had my backpack stolen after like I come back from work and I left my stuff, I had my backpack with me with other personal items that I don't know why I would be honest, but I was at a restaurant and in there I had some USB drive, some you know, kind of like checkbook type money that was worth like money in a way. And, and within two minutes I got stolen without me understanding, without me realizing what had happened. And when I found out about it, I guess you know, minutes later is, you know, I went home, called my, my bank and it was like an hour time frame that went through and my, my credit card had said that there was already like $3,000 charged to the account. So it was like, like really fast, you know, fast forward a little bit. I later went back to the restaurant and find out that the couple that had taken my backpack were like very elegantly dressed, you know, like suit, black dress. And you could never tell just watching these people that would be the kind of person to do that. So, so it was like that kind of identity is what I realized that caught me more to pay more attention to security. So then from there I really started getting more into cyber security, getting myself more involved. Went back to my masters in that left Cisco, went for United Airlines, did got my role there as a principal cyber security architect supporting the IT side and ot, and
then from United came over to come and said doing the same thing. So right now do a lot of like the IT side, but also the OT side of, of infrastructure, critical infrastructure, supporting strategy, architecture, that kind of thing. So let's know my background.
5
00:06:02.000 --> 00:06:07.000
And Ronaldo is a big deal in Houston. So if you're in Houston, he's everywhere.
6
00:06:07.000 --> 00:06:10.000
Not really. Not as much as. Or Oren's Earth.
7
00:06:10.000 --> 00:06:11.000
I'm trying.
8
00:06:11.000 --> 00:07:59.000
Well, you know, that, that's the, the, the funny thing. And, and I get the opportunity to sit across from, from awesome folks like you guys and you know, everybody has a journey that gets them there and, and our experiences bring value, right? It's, it's why true diversity on your team is people with different experiences, because those experiences can help me see things that I don't have. I've never been exposed to. So I don't think about the, the, the, the things that Oren has when he was crawling around in the bottom, you know, in, in the basement of, of a, of a, a ship or whatever IT is, right? Those are things that he's going to bring into the operational side when we're looking at cybersecurity. He has that perspective that, that others don't. And that's why one of the things, for me, that's why I see OT is difficult. It's not hard. The technology side, as Orin is doing with his, his demonstrations in his labs that he's building out now, right? He's showing people like, it's not, it's not hard. It's really not that difficult. That's not the point. It's understanding the why. Why do we do things differently. Why Is the impact different? Like, why do we secure things differently? Why do we have open protocols? Like, why do we not, you know, have. Why do we not lock our, our control room workstations? Like, why do we leave it wide open with no passwords? Like, these are things that, from a security perspective, if you only looked at the security side of things, you're like, oh, my gosh, your front door is wide open. You're like, yeah, but it's in a protective environment, and there's three other doors that are blocking it, and there's a security guard, and I have all these other mitigating controls. I'm not really worried about that. It's more important that the operator can actually control the thing that's going on than it is, oh, gosh, what's my password? Or Bob went to the restroom. Who can log in to turn this thing on or off or adjust something like, that's a bad situation to be in. So that's true.
9
00:07:59.000 --> 00:08:56.000
And, you know, I was reading actually about Bell Labs. I don't know if you heard of Bell Labs, but they invented almost everything you see in a computer. It's amazing the amount of innovation. And the guy was saying it was, I forget the book. Innovator, something Innovators. But the guy was saying, like, Bell Labs. It wasn't one smart person like Elon Musk, you know, that just comes in there. I know he has a team, but you know what I mean? It wasn't one person that drove it. It was. You had a PhD in physics on one side that maybe didn't know how to use a screwdriver. And then you had somebody that spent 30 years climbing telephone poles and running telephone wire. And then you had a guy electrical engineer, and all these different, varied people, and they all came together and worked together in the same spot, and it just accelerated, which I think. I think OT needs that. Yeah. And that's, that's why I'm doing what I'm doing. And just bringing as many different people together as possible is what we need to light a fire and, and get
10
00:08:56.000 --> 00:08:58.000
this thing burning 100%.
11
00:08:58.000 --> 00:10:58.000
You know, like. Like something also related to that. Like the other day when I met someone on someone, one of these events I go to here in Houston, and they were asking me, like, so why. So why ot? Like, no, like, you have like a networking background, architecture it. So how did you get into ot? Why do you like ot? Why don't you want to be in it? And I didn't really think about it because there's aside from just liking cyber just the way it's so dynamic and evolving and it's always changing, like just the way it is. It's. It's almost like in a way think about, you know, for example, like my, my wife, my sisters, they're like into dust and stuff. So it's like kind of like gossip. Cybersecurity is always something happening. You want to know what's going on, so you want to pay attention and get the scoop, get the details. And being able to be part of that is just, that's one aspect to it. But like the other part that, that made me realize that like ot, why OT and why do I enjoy doing it? When I was at United and just thinking about the way the infrastructure is and, and, and how OT is very sensitive. Our whole, you know, legacy and things that I. You can always fix it the same way like it. But it's pretty comfort and being able to. My perspective is, you know, if, if, if at that time when I was in aviation, my family's flying on planes, you know, I haven't fly on planes. Friends and other people are flying on planes like that. Safety is so critical that we gotta do what's necessary to protect. Now, of course, now there's a lot that goes into it in aviation. There's a lot of very, There's a very regulated. A lot of security by like just in general thinking like about the chemical, the utilities, you know, energy, everything. If, if, if this gets reach and bring and, and they attack in a way that causes an impact. That's talking about people's lives and safety. So for me, that's kind of like a driver. Like, you know what? I can't. I may not be in these other industries, but, but I mean, aviation, manufacturing, we got to do our part to really protect and everything that we do a little bit here and there with our peers all makes a big difference to try to help modernize where ot security can get better.
12
00:10:58.000 -->
00:12:29.000
Yeah, 100%. And I always give the analogy. I'm sure people, if you've listened to my podcast, you probably heard me say it at least once. But you know, it's the, the control system in the, in the airplane has, has a vulnerability and you're flying 30,000ft in the air. Do you want to update that while you're flying? I, I don't, I say, I say we land first. Yeah, it's probably fine. I don't want to risk it. Like that's the thing in ot, it's just different, you know, again or in Coming from, from the military, you, you talk about ships and warships and a submarine or something like that. Like, you've got to be really confident and, and obviously a lot of those things, they have, you know, secondary and tertiary systems that they back up and all that kind of stuff. But still, do you want to be the reason this thing goes down? Because you pushed a patch that, is it really critical? Like we're, we're, you know, a mile underneath the ocean. Do we need to update that right now? Or why don't we wait till we get to port before we do it and make sure that it's in a safe environment. It's why we do a lot of things in OT and outages. Like if I'm going to make big massive changes or I want to do a pen test or something like that, I'm probably going to wait till an outage or at least when it's a non critical time that if it, if worst case scenario happens or, and you talked about this last time, right? You know, you walk in the room and you know, some PLC trips and they're like, hey, you just tripped the plc. And then when you got to the actual information, you said the guy was like, oh yeah, no big deal. It happens every day around this time anyways. You're like, okay, well couldn't you have led with that instead of telling me that it was my fault?
13
00:12:29.000 --> 00:12:31.000
That's my favorite story.
14
00:12:31.000 --> 00:12:41.000
Why don't you tell the broader story? Because you told it last time, but we got cut off. So I'll, I'll put it as a short, but it's, it's still a really good comment to, to really understand.
15
00:12:41.000 --> 00:13:52.000
Yeah, I'd love to. Yeah, it's my favorite story. So, yeah, we were, you know, you've heard active, active scanning, right? Is active scanning safe? Is it not safe? One week it's safe, the next week it's safe. And I, you know, we, we were doing some active scanning on a client and we went through and I am very careful because I've been the guy on the plant floor, like you're saying, I've been the person on the Navy ship, I've been the person on a drilling rig drilling into Mother Nature's energy source, which is not something to play with. And so we're, we're doing some active scanning and I had explained to them, like, we're going to use a safe protocols and we're going to limit the network throughput and all the things you would say. And halfway through you said, hey, you just tripped off my plc. You need to stop. And I was so embarrassed. And I stopped my scanning. And I'm apologizing. I'm, like, stressing out about it because it's a major deal, you know, to. Because I was trying to be so careful. And then the guy was like, oh, yeah, it happens every day around this time. I wouldn't worry about it. And it got me thinking, like, when. When you're active scanning in your environment, you are responsible for every bad thing that happens for the next two weeks. Like, it's gonna. Even if you stopped and you're gone, they're like, oh, yeah, they scanned. And now my. My system is tripped off for the fifth time this month. Like, it must be their fault.
16
00:13:52.000 --> 00:14:26.000
The last thing that's changed, right? You know, they're looking at, you know, from the pre. You know, I think I told the story last time, but, you know, the pre job brief, if. Even if they're just talking about, hey, Oren's gonna be doing active scanning today. If something happens, even if you haven't started yet, if something happens, the first thing in that engineer's mind is going to be like, hmm, pre job brief, Orange's gonna be scanning. That's probably it. He broke something. Let me go find Oren and beat him until he fixes whatever he's doing or stops breaking things. Even though you haven't. Like, you're still in the break room, you know, drinking your coffee. You hadn't even started yet. But it's still your fault until you prove it's not.
17
00:14:26.000 --> 00:16:21.000
That's true. And that's with everything I've ever done in my career, even adding a firewall rule or installing endpoint protection. If something happens. Like your thing ruined my. Yeah, it's. It's very funny. But also, I'll tell you the. This is a secret. Don't. Don't tell it. No, I'm just kidding. This. I think what separates a master craftsman from somebody starting out and somebody maybe starting it out in cyber is the way you reframe it. So, like, if I were to tell you, well, I'm going to sell you this software. It's secure. We know as cybersecurity. Nothing's secure. Okay? There's. There's just different levels of security, right? And you tell me what you do to make it secure and what I need to do to make it secure and what to do if something happens, right? And that's. That's how you have that conversation. And in safety, when you go to the plant, it's the same way. So instead of saying, I'm going to active scan your network, it's safe. What you should say is there is risk anytime you do anything in the network. But we're going to do this and this and this to limit that risk. If you see anything, you could do this to limit the risk and let me know. And as soon as you see. You know what I mean? So you have a conversation about, this is what could happen. This is what I'm going to do to lower the risk as much as possible. This is what you could do. And if it happens, this is how you could lower the impact. And just like any other CISSP risk conversation. And when you tell to them like that, then they're prepared for it. They're like, okay, I'm invested. I think that's a good idea
to go ahead. Then when something happens, they don't always jump your butt and say like, it's your fault because they were part of the conversation, they're bought in. And I don't know, I just have a much easier time about it. But you don't see that a lot. Like when you see the marketing material from vendors, they say it's like safe scanning. And I think that's not exact, not a good message to say. I think it's more nuanced and you get a better result when you're just honest about it. Like, so that's my soapbox.
18
00:16:21.000 --> 00:16:49.000
You know, Aaron, that's. That's a very valid point, though. I. Sorry. It's a very valid point because if you think about also from the time that you've been doing it many years ago, scanning, that concept of a scanning of what it is, what it means and how it's relayed from like framing to the way it is now, you know, before used to be where, let's say, you know, a couple years ago it was, yeah, this is, you know, same, you know, scanning prote. But now the language is changing to
19
00:16:49.000 --> 00:16:50.000
say, well, we're pro.
20
00:16:50.000 --> 00:18:10.000
It's a query, it's a pro. We're not doing scanning. But it's, it's how we're using OT to talk to ot. You know, vendors are catching up. You know, they're, they're realizing that too, because it's true that the message, how, how they present it and to say, oh, this is a safe scan. Like, like you said, not 100%. Like, can you guarantee 100% that is really safe? You can imply yes, but it's, it's really the matter of, of how it's implemented what is being done, what exactly is involved in part of that scanning and, and they're catching up to this. So, so the framing is, is getting better how it's being described as a capability across these different solution is making a big difference you know from that perspective. But also the education like, like, you know, like you may can give along with their peers when we talk to the business is help them understand it's not that kind of IT scan. It's not like we're doing an end map in that way. You know, we're doing it, you know, using the mod buzz or we use whatever protocol to talk to this environment that they already speak the same language. We're just communicating to say hey, tell me about yourself. You know, what are you doing? You know, what do you have? So it's, it's, it's getting better and just the more we do it then, then it just doesn't get there more. And it's of course gonna also have an impact with. Whenever you say AI is doing it's well another animal.
21
00:18:10.000 --> 00:18:12.000
So how'd you say it?
22
00:18:12.000 --> 00:18:33.000
Yeah, that's something. It's like that AI word or the scan word has just been especially in ot, it's like a bad word. Don't say that word. Don't put it in your marketing. Don't say you're doing it. Like in fact you want to say we're not scanning. We're going to, we're going to probe. We're going to interrogate like any other word that means the same damn
thing. But you can't say scan.
23
00:18:33.000 --> 00:18:34.000
That's true.
24
00:18:34.000 --> 00:18:35.000
Yeah.
25
00:18:34.000 --> 00:19:16.000
And I actually so to go to our OT secon talk which I thought was, I thought it was super fun. So we did kind of like a boxing match and I was the like consultant pen tester and Reynaldo was the asset owner. And so in this instance I may be banging around in his network scanning or probing or however you want to say it, but he is the one that's going to get the call. He's the one that's accountable for my actions. And so I thought that was a really good conversation like of what, what I do and what he does and how our perspectives differ and how like I get excited when I find vulnerabilities and he's like oh crap. So yeah, it's just a good, maybe he gets excited too. I don't know.
26
00:19:16.000 --> 00:20:26.000
But so you know, walk me through that. Like what did that look like? And what did that. You know, how, how are, how is that messaging Helping, because we always do, and I say this a lot as well, we do business at the speed of trust. So the faster that the Orin of the world that's going in to do their thing can make Ronaldo actually trust him, the more likely he's going to allow you to do the thing you're going to do do. And it's not because Ronaldo thinks there's zero possibility that something bad can happen, but he has a pretty good confidence that a, if something bad happens, I'm aware of it. Orin is not going off rogue doing things we didn't talk about. He's doing things within this box. That doesn't mean the risk is zero. But I know what the risk is in this box and I, and I know how to respond to that thing. Whereas I've seen other folks that say they, they convince you, like look over here and then they're trying to not let you know that they're doing other stuff. And yeah, you may get some, some data, but you're also losing that trust. And man, that, that's not a place you want to be in, especially in ot because you do it once and you're out the door. You're never, you're never allowed on site and anybody else's site for that matter. Again.
27
00:20:26.000 --> 00:21:57.000
Yeah, you know, you're right. When it comes down to, I think it's a few different things. You know, when we had that conversation we were talking about, you know, like, yeah, trust is a very big product. It's got to be very clear the expectations, you know, what rules that they got to follow. You being transparent, you know, us, us on, on the, on the asset owner side. We also have to be clear about what we want, you know, how much, you know, you know, what kind of perspective of that pen test we want to do. You know, if it's something, you know, external, internal assume reach, you know, there's different, a lot of different factors that go into it. But it's not just say if I'm the one engaged with Orin, it's not just my input or, or my requirements I'm considering. I have to have those internal conversations to get
that alignment and say like, hey, before I even share with or in all the details, here's the things that we want to address. Maybe it's driven by just cybersecurity initiative. It could be an audit related, it could be something, you know, tying back to clients or it could be something that we get pulled inseparable but there's different stakeholders that you gotta Consider and getting that right alignment expectation that we want to do these things, to see these kinds of outcomes or these kinds of information want to address, then it's sharing that piece of message to someone like, like Oren, whoever's going to be doing that pen test so that we can have that transparency, so we can have that information of what we want out of the results, you know, during the results and then what comes after
28
00:21:57.000 --> 00:24:01.000
and getting that action done and that goes into like. I think a lot of what we talked about in the talk was just how to be creative about it, right? So people say don't ever pen test a live plant. Which I actually agree with. You don't want to pen test, you know, your plane as you're flying. But what you can do is maybe set a hypothesis. Like I, I want to know if there's any protocols that can lead to compromise, right? Like these Windows protocols like NetBios or Link, local link name resolution. The, the, there's some protocols that, that will, Windows will just hand over their hash. Like if you use a protocol, right, and so you could get a passive network traffic and see if those protocols exist. And if they exist on the network, then you could say, well, since they exist on the network, I know I could probably spoof them and get your hash. So you don't even need to really be on the network. What you need is somebody with evil mind, somebody that, that thinks red, that can look at it and, and run a hypothesis and find weaknesses. And you don't necessarily have to own every box. You can gather the information you need to validate whether that weakness exists. And there, there's, you know, your top 20 weaknesses and if you got those covered, you're in, in better shape, you know, pretty good shape. But when I actually go on pen tests, usually the top 20 are not covered. Like there's something in there. And these are places that have spent millions and millions of dollars on cybersecurity. And they're really talented, really talented ot cybersecurity professionals. But we all have blind spots. And so having somebody that has a different perspective outside of yours that can help you identify where your weak spots are that you don't see, can really bring a lot of value and make sure you're not wasting a lot of money on something that maybe you're not ready for. Like super advanced vulnerability management system when maybe you have a very easily guessable domain admin password. That's the one I used in the. And I had this, I had this gif of this. It was A teenager learning how to drive and they look in their blind spot and there's actually somebody there and
29
00:24:01.000 --> 00:24:05.000
they're like, what are you doing there? Why are you there? Right.
30
00:24:05.000 --> 00:24:06.000
It's.
31
00:24:05.000 --> 00:25:09.000
The analogy I've used as well is like, you know, you don't, you don't put a paint job on a car that doesn't have a motor in it. Like, you know, more than likely if you go buy a junker car, the first step is not to put a paint job on it. Let's probably get it running first and then we can sit. Now obviously if you're building a custom car that doesn't, that analogy doesn't exactly work. But, you know, you get the point of what I'm trying to make there is like prioritize what you're doing and don't just go buy the latest AI thing. If you, if you don't have basic segmentation in your network, like the talk I gave it at DEFCON in Singapore was really just the basics. Like, do you have an asset inventory? Like the, the sans five critical controls, right? Just basic. Do I have secure mode access? Do I have an asset inventory? Do I, Am I segmenting my network away from OT and it. Am I segmenting systems off, like just the basic level things that don't have to be expensive and I don't have to do a pen test to do those things. I can probably determine what's going on in my environment and make big changes by doing some of those really, really basic items.
32
00:25:09.000 --> 00:26:16.000
And the only thing I would add to that is, and what, what I recommend is, is I've seen people, we all have what we like to do, right? So some people are asset inventory people and they're like, I'm doing the basics and they spend their whole time getting asset inventory and they're looking for that last host on that subnet way down in, in Costa Rica, right? And other people are vulnerability management people like, oh, let's do the basic. So what I find interesting is that like it's 80% of the value you get from 20% of your effort, right? So just getting the first 80% is a huge step. Then go on to like you're saying, get 80% of your asset inventory, then get 80% on network segmentation and the pen test will help you say, hey, you're actually, you know, 10% on network segmentation. You thought you were 80, but you're actually so. And I, I'm seeing a lot of, actually we're seeing growing demand for that. Like, people are, are Wanting their systems tested and in like it used to be like risk quantification and all this stuff. Now we're seeing a lot of like, don't, don't tell me, show me. Like, I think. And that. I think that's really exciting because that's what I like to do.
33
00:26:16.000 --> 00:26:17.000
Yeah, for sure.
34
00:26:17.000 --> 00:28:24.000
Something else too like, like this thing about you guys have segmentation piece and visibility. The way I also look at it when it's apprentice, it's also like validation too and, and being able to architecturally visualize but, but proactively also plan with where what's your target state, local, you know, like, you
know, one of the things that when it comes, whether with a pen test or just in general, you know, seeing hey, where are we? You got to have also, you know, the asset owner side. We got to have a good level of understanding of your current state. And it's not just some areas and technology like oh yeah, we know we have firewall, we do segmentation. But look at the bigger picture is what else do we have in place that support reports all these different areas that, that would be areas of consideration from a pen test report because you know, different findings can mean that, that you got to improve your, your visibility, that you got to improve your, your controls for remote access or, or how granular you get with segmentation. If it's east, west, north, south zones, you know, DMZs and even just access to devices or, or hardened of systems man. And it really also takes, it's a very collaborative effort from, from what I see is that you got to know really well the environment that you're trying to assess and also have an idea proactively that says, you know, this is where we want to get to today. We're here. We, we know or we expect we're doing these things to some degree. It might be, you know, good, you know, not as great or just complete lacking. And we want to know what does this output show us that can tell us oh yes, we're doing this right. Or, or like you say, you know, you, you think you're doing 80% but you're doing 10% segmentation. And that's a point that would help you. So, so really knowing the architecture environment is a critical piece to see. You know, did it make sense or was there a value in doing that Ventus report? And a lot of times you can have that as long as those details are there and that acknowledgement between the asset owner and the pen tester and what you're expecting, what you Share is very clear from up front.
35
00:28:24.000 --> 00:28:28.000
Yeah. And. And the other piece of that, that, the. The trust thing that we talked about.
36
00:28:28.000 --> 00:28:29.000
Right.
37
00:28:29.000 --> 00:28:49.000
So when I'm doing these assessments or red teams or whatever you want to call them, like, we're walking in and I'm. I'm sitting down with, with folks that are. They're doing a good job. Like, they're, they're. They're doing the best they can. They're. It's not like I, I try very hard to communicate like, look, I'm not here to tell you that you suck at your job or that your baby's not ugly.
38
00:28:49.000 --> 00:28:50.000
Right.
39
00:28:49.000 --> 00:30:10.000
But what I am here to tell you is, is to your point, Orin, I may see things that you don't. That doesn't mean that you're bad at what you do. It doesn't. None of the things that I find are to be like, aha, I'm smarter than you. Like, no, that's not the point. The point is, is that we may find things that you didn't know or that it's that trust but verify, like you thought you were at 80%. We're going to show you these other things. It's not a, hey, you're bad, Orin. It's really just to say, hey, here's some things now let's go fix this. Them together. And if, if those folks have that. That mindset and they're open to that, then. Then it's amazing how much you can get done. But when they're defensive and they're like, hey, you know, well, the. Any. Any rule in the firewall is at the bottom, so it's not really a problem. Like, yeah, it, it actually is a problem. You shouldn't have an. Any. Any rule in your firewall ever anywhere in your firewall. And there should be rule. Like, I mean, there's just obvious things that you shouldn't have to justify. But when somebody's trying to defend it, it's like, I understand why it's there. I've put in any. Any rules myself. Couldn't figure out what the heck was going on. The plant need to be running. That's a way to make sure it runs. We put it in and it ran for a couple of weeks, but in the background, I'm like, I know that doesn't need to stay there and we need to remove it because that's not a good thing to have because I basically just turned this firewall into a router.
40
00:30:10.000 --> 00:30:15.000
Yes, yes, I. The good old Indian evil.
41
00:30:15.000 --> 00:30:17.000
That's right.
42
00:30:17.000 --> 00:31:44.000
More Than more than what they would like to out. You know also to, to, to go with that. Like there's, there's, there's even considerations with you know the Indian rule is very commonly like to see like with those routers, right. I mean the firewalls. But in something similar can also happen at the lower levels if you're using those kind of ACLs and filters down to your switches or even routers in some cases, you know, where they're kind of acting like firewall kind of kind of role. But those from time to time you get can get very long and, and messy. You know, if you're always having to manage that or update them or, or like make an exception. Okay. You know, let's, let's. We're gonna make exception to put it this time. And then these one offs become consistently want that that happen. And when it comes down to that level of rules segmentation, you, you got to get to a point where you have to reassess or start looking at capabilities that will be able to then take the way you've managed the network those rules that can now do it in a more logical way without having to have all that administrative burden. So for that you got to have the right level of reaching out to see what solutions out there can do this. But just because one said we can do it, you got about it. Gotta check to make sure that it can actually do what it does. So there's a lot of effort that goes.
43
00:31:44.000 --> 00:32:39.000
And then you get promoted and this poor guy comes up and takes ownership of all this stuff. All these exceptions. I think that's a problem. That's a problem. I see in it a lot ot nobody gets promoted. Everybody's. Well, I mean people get promoted. But you're at the plant. Everybody knows the plant so well. Like that's my favorite thing about like when I
find somebody at the plant and they like hear a noise and they're like oh, that's a number two fire pump. I'm like for real? You know that's a number two fire pump. By just that sound they're like oh yeah, that's number two fire pump. Or like yeah, what was I saying? Yeah. So those kind of people you find in ot, but in IT generally people are moving all around and people leave the com. You know, the CISO is in place I think an average of two years maybe. So just as soon as he's getting you know segmentation project takes years in OT usually. So just as soon as that thing is rolling out, he's quitting the next guy comes in and says, what is all this? Yank it all.
44
00:32:39.000 --> 00:33:41.000
Yeah, that's not my vendor. I don't like it that way. Let's do it a different way. Let's adjust. Like, yeah, it's, yeah, it can be very frustrating. Well, and then the other conversation that, you know, again, I was a vendor from a, from a product vendor side, you know, I've got vendor X and vendor Y. You know, the CISO comes in or the new guy comes in. I like vendor Y better, whether it's a firewall or a, whatever the product is. And it's just like, okay, maybe it's better, maybe it's got new capabilities, whatever, but we haven't even finished implementing the one we have. Instead, before we start jumping ship and changing to something that's got better features, let's get the features out of the one that we already have. We haven't even deployed it all the way. We're not even, yeah, that's monitoring it. Like, there's all these things that we're not even doing. And you're already looking, looking at the next version of the, the, the, the competitors, like, I get it that they took you to dinner, but let's just stick with what we got until, until it's time to, you know, go down the road a little bit further than where we're at.
45
00:33:41.000 --> 00:35:32.000
The, the tool specialization piece is actually, it's an ongoing challenge with all the companies deal with like, or I'm sure you, you hear it too and you've seen it. But, but like when, like at these events, I talked to a lot of the different peers and leaders and it's, it's like, how many tools do you have? Oh yeah, way too many. You know, 40, 50, 60, you know, 30 something. And then you ask, well, how many are doing this particular area? And you could probably get like at least two or three called out that, that are doing those, those kinds of things, you know, and so it's, it's something that, you know, that, that part of, of rationalization and architecture, I saying, you know, let's look at what we have first. Like, I'm always in favor of, okay if, like, if you go into a role and you for gf, right into a company, you know, you already have all this tech stuff, you know, and depending what, on what your role is for that team, you know, depending, it might be that you have to look into it. But, but in our side with architecture, that's something that we, we want to understand. You know, we should
understand. We Got to know, what are we effectively using that are configured and, and, and doing for our roadmap and cybersecurity? But that aligns one to the vision, you know, the goals that you're trying to achieve. But when we have these tools, go back and reassess, okay, who are the consumers of that tool, what are they using it for, what kind of capabilities, what features do we have turned on that are actually being leveraged? And then start comparing that with all the other tools or your tech stack, and then you start to see where there's overlap, where there's gaps, and that starts making more sense and how you rationalize what you have in house? Or is there an opportunity to fill a gap that these tools can't do? Either a limitation or it costs extra money that you have to go and invest. That becomes a different conversation. But, but it's being that proactive to go do that. And it takes the right level of mindset to, to push that.
46
00:35:32.000 --> 00:36:11.000
Well, and, and as you, as you look at the, the bigger picture and a mature program like that, that's what you're talking about. Right? And some of these larger programs that we have, I'm gonna have, I'm gonna have the Venn diagram of capabilities, and there's, there's going to be. There's also going to be gaps, and those are the things that we're looking for. If I have an overlap, you know, sometimes having two different sources of truth is good in that, you know, this thing is telling me A, and this thing is telling me B, they should be telling me the same thing. Why am I getting different signals? Or, hey, they're both telling me the same thing. They Both say it's 73 degrees in my room.
47
00:36:11.000 --> 00:36:12.000
Cool.
48
00:36:12.000 --> 00:38:16.000
I've got my thermostat that says it's 73 degrees, and I've got a, you know, a thermometer on my desk, and they're both saying the same thing. That's awesome. Awesome. If the thermometer this says 80, but the thermostat says 70, there's a problem. Right. Because it actually is 80. And the, and the thermostat says it's. It's not. Right. So sometimes those overlapping things are good. On the flip side, from a, from a cost perspective, many times these things. Do I need both tools? Like what? Is there enough overlap that I can, I can reduce my tech stack and have fewer tools to do the 8020 rule that Oren was talking about? So there's all sorts of ways that you can look at it. And as AI comes out, I see more and more folks talking about how can I build an off the shelf custom thing that, that we support internally instead of going and buying the expensive things that are out there? And I do that obviously home in my lab and the things that I'm doing. But doing that in an enterprise level, especially an OT level, is a different thing. So those are, those are other things that I'm concerned on as we're talking about this. If I were to approach Ronaldo and say, hey, I can build you a thing that does what you're looking for exactly
right. And we can have one product, you build it, we'll build it together and it'll fill all of your gaps. And that sounds great and I'm not saying we shouldn't do it, but there's a whole bunch of risk behind that and beyond just the cyber thing. But who's going to support it when Aaron leaves? Who's going to support it? Like, how do we know that it's going to work and how are we going to, you know, stress test it? And all these different types of things that the reason you're buying these commercially off the shelf products is they've done a lot of those things or support around it. They've had, they've had the code and it's been tested and been gone through all these different Sock 2 analysis and you know, and they've, they've smoke tested it and all that kind of stuff that I think a lot of people aren't thinking about. Just because I can vibe code something and it works, then it's good enough to put in my production environment and depend on it again. I don't want it flying the plane for me. Not yet, at least.
49
00:38:16.000 --> 00:38:27.000
Yeah, yeah. Going back to what we were saying before, like active scanning was bad enough. If I vibe code something and I put it in there and lightning strikes outside the plant and kills all the PLCs, they're going to blame my code for sure.
50
00:38:27.000 --> 00:38:28.000
Yep.
51
00:38:28.000 --> 00:38:35.000
Like anything that happens in that plant is my fault. Like I've vibe coded this thing. Yeah. Anything that happens in there is going to be my fault, period. Forever.
52
00:38:35.000 --> 00:38:38.000
Oren's terminator just killed us all.
53
00:38:38.000 --> 00:38:39.000
That's right.
54
00:38:39.000 --> 00:39:52.000
You know the other thing too, like a lot of things we got to look at too, is how they complement each other too. You know, there might be, you know, there will be overlap and a lot of different capabilities and tools, like a lot of tools do many of the same things, but sometimes the same thing can mean the way it analyzes data, the way it captures it, the way it presents it, that, that is targeting a specific view or, or interest to say, some customers, some, some, some groups. But then the overlap they have another tool is presented in a different way. And something like you're saying like that overlap is not necessarily bad, but it's true. You know, there's some overlap that you might need, but there's also overlap that is. Well, categorically as a, as a section, they might be in the same group, but they're actually doing different things. They appear the surface to be the same, but they complement each other. And what one does and the other one offers or how they enrich each other. That's also key to look at these things from rationalizing what you have and being able to make those decisions. You know, where, where, where's our opportunity? Where is a way for us to fill gaps? Where can we expand and grow? You know, just. It just kind of depends on the use cases and, and how folks are
using it. You got to make them very effective and use them the right way for each other like that.
55
00:39:52.000 --> 00:40:44.000
And I go back to our pentest conversation, which I, I think people are coming around to, is that the, my next step maybe should be the one that somebody used to gain access to my system. Right. So then you could say, you know, I thought I had coverage here, but they got around my detection system or then that's where those compliments can come in. And maybe I want to add, add Windows Defender to. Since I could run Windows Defender along another endpoint protection. I can have both of them running or have two sources for my network detection or. But you, you, I think you have a strong business case if somebody used it to attack your system and you could kind of steer your, your investments like that instead of like trying to do it off of, you know. Yeah. Maturity diagrams or something like. That's what we were talking about in our talk is like the value you get out of it and the, the risks. Spend a lot of time on the risks, but.
56
00:40:44.000 --> 00:40:46.000
Well, there's a lot of risk there, right?
57
00:40:46.000 --> 00:40:48.000
Yes. There's also risk not doing anything.
58
00:40:48.000 --> 00:40:50.000
Right, that's true.
59
00:40:50.000 --> 00:40:53.000
Yeah, exactly.
60
00:40:53.000 --> 00:42:50.000
And that's the, that's the catch 22, right. To your point there, Ray, is, is, you know, the risk, the risk of doing something means I'm inherent, I'm bringing in these things. I'm changing my process. People don't like change. You know, I'm, I'm, I'm allowing somebody scary like Orin to come in and Scan my network. But on the flip side, not allowing Orin to come in and scan your network or penetrate or whatever, you know, interrogate, you know, talk nicely to whatever you want to call it means that you don't know, like putting your head in the sand and hoping that you're good isn't enough anymore. Right? We, we see, you know, 10 years ago when I was doing this to Oren's point, like I've been doing this longer than it's been called ot. When I first got into this, it was just the O, right? It was just, you know, hey, you, you under. You're in this power plant company and you know technology and you also know the operations side. We're going to put you focus on these things. It wasn't called ot. There was no, there was no industrial or Ottoman pro products in the world. Right? So when you're looking at these things, we have to think about like, what is the big picture of this? Like, what are we doing? Like, why are we here? And I can't just pretend that, that it's not going to happen. Like, we see these things in the news. We're seeing attacks hit critical infrastructure, we're seeing attacks hit manufacturing, we're seeing ransomware, we're seeing Colonial Pipeline type events. These things are regular events, no matter what. Some of the, the pundits will say that there's never been an OT attack. There's OT attacks
all the time. Just because they're not reported doesn't mean they didn't happen. I've personally been at more than a handful of things that are not necessarily public and I'm not going to obviously mention for those reasons, but they were absolutely OT attacks and they brought down very, very large critical infrastructure environments and, and there it happens. So doing nothing is no longer an option.
61
00:42:50.000 --> 00:44:09.000
You know, like, and to go also with that, it's also like the fear of knowing you have to then take action that's also kind of, you know, related. You know, you know, not doing anything is, has a risk. But then, but then you'll, you'll have. There may be some, some people, like I spoke to a few folks in these events were like, well, hey, you know what happens? Like, do you want to. If, if you do a pen test, you can use these results now, you know, there's something has to be done. And some responses I've gotten, some people is like, well, I don't want to, because if I know I now have to do something about it. And, and it's like, yeah, but I Get it. Because then now you're kind of forced. But. But it's like, just because you don't know about it doesn't mean that you're not safe from it or, or you're. Or that it's not gonna happen. Like, you need to know. You, you. It could be that you're not ready to do it, or you have the technology, but at least you're aware of it. And then you have a plan or ask plan action or. And at the same time, doesn't mean you're accountable for all those steps. It might be that you drive part of it. Other groups will be accountable. Maybe they're not ready, but at least they're aware and they can prioritize. But being fearful of knowing, being, I guess, oblivious to it, does not make you any safer than. Than just trying to be proactive. And that's a mindset.
62
00:44:09.000 --> 00:44:32.000
And to me, that's the same as. As if you've been in ot, the safety culture, right? So, you know, there's a reason why we do pre job briefs. We have safety briefings. Like, we have challenge coins. Stop. When unsure. Like, you know, we're. We're challenging. And a junior person can walk up to the most senior person and say, hey, this isn't safe. Stop.
63
00:44:32.000 --> 00:44:33.000
Right?
64
00:44:32.000 --> 00:45:29.000
You know that. That culture and you're. And there's no retribution from it. Like, if I'm doing something unsafe, it's not that I'm getting reprimanded. It's actually that I want you to be safe and go home, and I don't want you to get injured. It's okay that I'm getting reprimanded, quote, unquote, you know, told not to do something because it's not safe. I don't want you to stand in the chair to change the light bulb. I want you to go get a ladder and somebody that's authorized to stand on a ladder and change it out correctly. Yes, I know it's a pain in the butt, but that's. You can also fall out of the chair. Like, the little things like that are a big deal. So when. When we bring that culture in OT and we start including that same culture around the cybersecurity thing, it shouldn't be that I don't want to know. It should be that I do want to know. Doesn't mean that I can do anything about it. But even if I can't make a change, even if I can't buy a product, I'd rather know it's there so I can raise my hand and say, hey, by the way, we have this risk. I don't know.
65
00:45:29.000 --> 00:45:30.000
It's.
66
00:45:29.000 --> 00:46:15.000
It's, it's improbable that it's ever going to get impacted because of X, Y and Z. Or maybe I just don't have the money to fix it. But it should at least be documented so that we know that it's there. So if something does happen, then at least everybody knows. By the way, this thing is really flammable. Let's keep fire away from it so that if it does catch on fire, I should have a plan. Okay. If that thing catches on fire, the fire extinguisher is over here, and here's our process. I'd at least like to have a plan of what happens if that thing happens. The bad. The bad thing happens instead of just pretending I don't know that it's there, because you probably know it's there anyways and you just don't want it documented that it's there. Which to me is just a level of ignorance that is beyond acceptable.
67
00:46:15.000 --> 00:46:16.000
Yeah.
68
00:46:15.000 --> 00:46:43.000
So I got a question. I think it's almost an emotional thing. I know people that I know, some friends of mine, obviously not me, of course, because I'm perfect. I know people that don't go to the dentist because they don't want to know. Right. That's a classic thing. Of course, it'd be better if they knew either way, but it's an emotional thing and it's not something they know. It's not good. So how do you make people more comfortable going to the cyber dentist again?
69
00:46:43.000 --> 00:48:40.000
To me, it's a culture thing. It's just the same thing that we've done in the safety. And I think it's that same culture. If people think that they're going to be reprimanded because something bad happened because they were. There was a malware or there was an attack, or there was a vulnerability or. Or the PLC went down, then they're not going to tell you. They're going to try to cover it up, or they're going to pretend they don't know and they don't want to fix it. If they feel like that their environment is accepting that, we can. I can raise my hand and say, hey, there's a vulnerability or a risk over there and people aren't going to scream at me and. And I'm not going to get a whole bunch of chatter about it and we can document something again. It doesn't mean we have to change it. But that culture has to be One of acceptance, not reprimand. And, and, and, and we've done a great job at OT with that on again, I keep going back to the safety culture. You know, zero is the acceptable safety risk. Right? We want zero incidents like safety zero. That's what we talk about. I don't want somebody dying. There's no level of death
acceptable in my power plant. Right. It sounds stupid to say out loud, but we, there was a time when that wasn't communicated and that wasn't the actual official standing from. Not that they really officially accepted it by, but by not unaccepting it, however you want to say that they are by definition accepting it. So if we do, if we built that same mindset and that comes at the organizational level and it comes from the top down and the bottom up, they have to understand that if I raise my hand and say, hey, this is not safe. We have any, any rule or I'm using a netgear firewall or router or switch in this space and that's not okay. You should be able to raise your hand as a junior person and say that's a vulnerability. We really shouldn't be able to do that. That doesn't mean I have to rip it out and break the system. It just means it needs to be documented so that it can get put into the pipeline of how do we fix that long term so that that risk gets removed.
70
00:48:40.000 --> 00:50:57.000
There's, there's also like a one out of couple things that too. There's a few different factors that also make sense to me. I agree with you. You know, Bohar Leon, it's, you know, culture is a big part of it. You know, the, and I think to go with that, the culture, it also comes through the leadership style and, and how they allow or empower their employees to speak up and hey, hey guys. We're all, we all, we're after the same thing. You know, if this gets impacted on a part of a area of that site, it affects everybody because at the end of the day we all work for the same company, right? And so, so it's, it also comes down to that leadership, having the right message, the right comfortableness that you have in that team where you build that trust with your. Were with the, with your employees or the group, but also among each other, being able to maybe have like some kind of outing event where, you know, you get folks to mingle and have more, you know, team connect, connection, professionals that they feel comfortable with each other because it's also a personality. It's also Individual personality, where some people are just more shy than others, some are more outgoing, some of them are very candid in what they say, and others are just very quiet and being able to work around the different personality types, but empowering them say, hey, you know, I get this, but, you know, you know, help them to help each other and help themselves that they can speak up and share these things. And if you have a concern, you know, yeah, raise up your hand like you're saying, you know, hey, this might be an issue. Even if you're right, wrong, it's okay. But also send this patient, especially with the senior guys, that, hey, if a junior person says something that's saying wrong, don't, don't be condescending to them. You know, help them, support them, you know, let them grow, teach them. And we need to be able to offset that kind of support or I guess, or that kind of knowledge trend at the same time. So, so it goes back to the style team, the, the mechanics, the chemistry of the team, of the individuals. But being able, I think a big part with your culture is, is that empowerment. They gotta feel like they are valued and they are valued and to be able to be empowered to help bring those things to, to the attention of
71
00:50:57.000 --> 00:51:06.000
the race, maybe even expected to, right? Like, I expect to know where my risks are. So you need to tell me, like, don't keep it a secret. That's what they said in the Navy, don't keep a secret.
72
00:51:06.000 --> 00:53:01.000
So, yeah, I mean, going back to that, right, it's, it's in the safety culture again. I think about power plants when we're doing outages, the whole goal that we're communicating the whole time, maybe a three month long outage. And the whole point is safety. Zero safety, zero safety, safety. You know, that's the first and only goal. And the safety team would actually have a budget and at the end of the outage, if we had a safe outage, then there would be like a giant party and they would have like a fish fry and they'd bring in barbecue and, and they would feed the entire outage staff. So it's, and, and it's like whoever did the most, you know, safety briefs, like if, hey, if I saw Orin doing something unsafe and I, I wrote him up about it, Orin and I were talked about in a positive way. And because I submitted that thing, then I got added to a list and may, you know, a gift card or a day off or an hour, whatever that thing is. But to your point, it's all about that, yeah. Shotgun. There you go. It's all about that culture and enticing people to say, hey, not only is it, is it okay? It's actually demanded. Like we demand that we do this. Like, no incidents. Like, it's like your phishing attacks, you know, when you're doing the, the fish me or you have the campaigns, like instead of getting on to somebody, if they click the link, because the links are really good now, so it's very easy to happen. Instead of that, let's entice them to be looking for it. And if you, if you, the. Whoever, you know, reports the most phishing things, you know, gets, gets the Apple, you know, new device or a gift card or whatever. Now obviously there's some things you got to go into that. And I'm not telling you how to do a program because people could take advantage of that and sent, blah, blah, blah, whatever. But you get my point. Like, it's all about the, the, the, the earnesty of doing this with the right reason. Right? And the communicating and making it fun and making it be something that is not looked down upon.
73
00:53:01.000 --> 00:53:04.000
They finally got me, Aaron. I finally took one.
74
00:53:04.000 --> 00:53:05.000
It happens, man.
75
00:53:05.000 --> 00:53:07.000
They finally got me after all these.
76
00:53:07.000 --> 00:53:12.000
But why did you feel embarrassed? Right? So that's, that's the mindset that we
77
00:53:12.000 --> 00:53:21.000
gotta
understand no better. But you know, nobody, nobody jumped on me about it. Nobody. I don't even think anybody knew about it, but it was definitely like, ooh, that's a good one.
78
00:53:21.000 --> 00:54:28.000
But yeah, and it happens. It's going to happen to everyone. Everyone's going to click one. Like, I literally reported one this morning. But they, with AI and everything else, they're going to get better. We have. We expect to do things unsafely, we expect to get injured, we expect, you know, incidents to happen. It should be the same around cyber security and we should have a culture of, okay, what could we learn from this? How can we make sure that we don't do this again instead of saying Oren, how could you. How are you so stupid that you clicked on this link? You weren't sure? Yeah, it should be. Okay, well, how did. If Orin could click on this link, imagine how many other people probably clicked on that link that aren't in cyber. How can we make sure that everybody learns from this so that it doesn't happen again? Right? That's what we should be thinking. It shouldn't be. How dare you, Orin. It should be, oh, wow, Orin, tell us what made you get, get hit by this? Like, how did you. Of all the people and as much experience as you have in this, explain to us how that happened so that we can make sure everybody else thinks about that and looks at it the way that you didn't this time, but maybe you can next time.
79
00:54:28.000 --> 00:54:30.000
You offered me a free T shirt.
80
00:54:30.000 --> 00:54:31.000
There you go.
81
00:54:30.000 --> 00:54:31.000
Clicked.
82
00:54:31.000 --> 00:54:33.000
So now, now you know how to get Noren's inbox.
83
00:54:33.000 --> 00:54:35.000
That's right.
84
00:54:35.000 --> 00:54:36.000
But awesome.
85
00:54:36.000 --> 00:54:58.000
Also I figured that another reason I wanted to I submitted for this was that Ronaldo and I gave that talk on at OT Secon about pen testing. Conversation between asset owner and pen tester. It's really awesome. But Reynaldo is also super into bringing up the next generation, so and I wanted to talk about that and then what I'm doing in education and how
86
00:54:58.000 --> 00:55:24.000
it all works together 100%. So definitely let's, let's dive into those. I I One of the reasons I do this podcast is because of exactly what you just said, Oren, is to give back. We need more and more people coming up understanding these convers. So love to dive into those things. So Ray, what are you doing and how are you bringing more and more folks into this space and training and learning and, and all the, all the goodness that, that we need because we need more people.
87
00:55:24.000 --> 00:59:32.000
Yes. You know, actually I was talking to Warren about this sometime back and a few others, but yeah, so like I, aside from, you know, in the field of cyber security architecture, ot, I also teach classes at Lone Star College, but the class I teach, I been teaching, I guess you can say, what, 15 years? Yeah, about a little over 15 years now. And it's more like evening type of adult. Mostly adult actually now it's, it's a combination of folks that are either in the field of IT or some kind of cyber or even non it, non cyber and people are coming into cyber. I started teaching first in the networking side. I would teach the CCNA CCMP courses and then for the past several years I've been doing now cyber security like Fundamentals of Cybersecurity, like, like the CCNA Cyber Ops course, the Ethical Hacker course and those the way I mean those course are taught based on the content from, from those modules from Cisco and then from, from the MindTap sanguine program that we use. But, but it's like, well when I have some conversations with some students, like I did one a few weeks ago, I did a presentation for, for, for the college where the want me talk about cybersecurity and AI and, and so just kind of taking the experience of what we go through as, as cybersecurity leaders and background and then where AI is at and where it's going. Just talking about the pros of how AI cyber kind of mingle and what it does with offensive purposes and defensive purposes, you know, both pros and cons. But the, the idea there is, is trying to show students that you don't have to be a lot of exposure and it. Or cyber to get into cyber. You know, you just gotta have the interest. And, and, and that's where I like to really try to help them is, you know, what, what are you interested in? Like, what are you doing now? Because a lot of the question that they give me is how do I get into cyber and how do I know what I'm like, what of cyber do I do? And, and how can I learn more about it? And so one of the questions I ask them is, well, what are you doing right now? If it's cyber, great. If it's it, great. But what do you do? Like, what are you into? What are your hobbies? What do you know about. And just, and based on the response, taking that and say, well, if you think about it, you already know a lot about, let's say, let's say building a car, let's say, let's say someone's coming from, from being a mechanic and they know all these different parts and how they connect. I go, well, do you, can you tell me like what parts are electric that you can figure on this little debias, some kind of, you know, configurable option? Well, those are actually related to it. So if you know the inner work of this, of being a mechanic and these different, well, you know how it's supposed to work. You know, the way if you do these things right, it does what you expect. And if you mess up here, it's going to break or cause an issue. Well, put your bad guy hat on and say, if I want to be malicious and I want to intentionally break this, I know that I could do XYZ and, and you know, what works, what doesn't. So cybersecurity is kind of same thing. You, you want to know how can you defend and protect something and think like a bad guy that would try to break it, but knowing how they
would do it, because you have that background now, you can go into that defensive approach. So, so if you think about it, you're already in the space. You just got to now learn some of the terminology of the basis of what cybersecurity is. The terms, you know, what is a black whitehead and what is a, what is a virus and OT and all these other areas just learn some of these concepts. But now you can get into this field so different domains and learn the basics, how these things work with one you already have. And then you just grow and just being able to go through that. So a lot of that from the education side is trying to give them those real life examples and, and showing them well that you can easily do with this part of technology and then how you get into it, it's just, it's just the interest starts here. You gotta have that interest because you will struggle. Is it gonna be easy? Some yes and no. Is there a learning curve? Yes, it depends. But as long as you're determined and you're interested, doesn't matter. You can get, everyone can learn, you know, 100%. You gotta build also on the social.
88
00:59:32.000 --> 00:59:34.000
You also got yout.
89
00:59:34.000 --> 00:59:35.000
That's true.
90
00:59:34.000 --> 00:59:35.000
Yeah.
91
00:59:35.000 --> 00:59:36.000
Youth is awesome.
92
00:59:36.000 --> 00:59:39.000
So and attending those is another way to learn well.
93
00:59:39.000 --> 01:01:12.000
And as I've built out teams in my past and current even whether it's at, you know, ey or as an asset owner, like early on when I again, when I was an asset owner, hiring folks for this OT stuff OT word didn't exist and I needed to find people that could fill the roles that I had. So it was really hard to find somebody that had the skill sets that I needed. So I was looking out to skilled, you know, labor type folks because I'm looking for a mindset. I would rather have a mechanic or an electrician that can problem solve. Because a mechanic is good at what troubleshooting. Like you bring in a car. Most people don't know what the heck is wrong with it. They're like, I don't know, it's making a noise and it, it seems weird. And they're having to figure out what the hell that means and deduct what's going on in this, all these components and systems in this car and say, oh well, your alternator's out or your front wheel bearing is bad or whatever. Mechanics are great, amazing troubleshooters. I can teach you technology. It's harder for me to teach you how to troubleshoot. It's harder for me to make you have a questioning attitude. That's something that's very difficult to teach. So somebody that has that as a skill, I can teach you how to subnet and cli and what commands to do on a firewall and all that type of stuff. It's harder for me to do the that mindset. Of troubleshooting. So finding those people that have that capability doesn't mean that you can't. I'm just saying if you have that ability already, it doesn't matter what your past is. I can teach
you the technology stuff and you'll be really good at.
94
01:01:12.000 --> 01:01:17.000
That's so true. Never thought of that. That is true.
95
01:01:17.000 --> 01:01:45.000
It's why, it's why you. It's why Oren, you came from this, right? You started on the operation side and you were troubleshooting. Something's not working. So you're tracing wires and looking at voltages and. And you're just going through a process. Yeah, there's documentation and things, but a lot of times it's just trial and error that, that, that translates directly to technology. It's just doing it in, in, you know, ones and zeros and bits as opposed to physical wires. But it's the same process mentally.
96
01:01:45.000 --> 01:01:48.000
And that is super addictive by the way it is doing.
97
01:01:48.000 --> 01:01:52.000
That's which leads us to your labs and the things that you're doing, Oren.
98
01:01:52.000 --> 01:04:39.000
Yeah, Very cool. Yeah. So I got this kit here, if you could, if you're watching on video. It's pretty awesome. And yeah, so this, what this kit is, is it's. I'm building an entire OT system from PLC wiring, the physical process all the way up to now I have an ignition hmi. So that's a Linux server. And then I have network security monitoring on top of that with open source tools, Suricata and Zeek. And then I built industrial DMZ with a firewall and a, a web proxy. And these are all things that you would find in a real OT environment. And I walk through how to build all this on YouTube, live on the work stream and next week or I don't know when I'm going to do like you did a guacamole remote access server. And then I think I'm going to do grass marlin and I'm just going to keep going and going and going with all this stuff and there's a little cadre of us and we are building these kits together and so it's like a little community of all kinds of people. It's crazy, the diversity of people. Some of them have been in industry, in OT for years, some of them have been in it and I want to move over and some are right in either high school or college, so a wide variety. And I'm getting a lot of joy out of it just because I think when I first started in this career or when I moved into OT cyber. Like you're saying it's hard to find OT cyber people. And it felt good because I was like the one guy with the, with the candle, you know what I mean? I had the light, nobody else did. But our industry is suffering because of that. Because you can't really make a big fire when you have one guy with a small candle. But so my, I think my situation, everybody's situation would be better, even my career wise, if we had more people in OT and more people like Reynaldo at Asset Owners understand it. And so that's what I'm trying to do with this kit. And my new favorite thing to say is the most important next gen tool you can have in your business is the next generation of human. And so that's the real next generation. And so I took that picture of me with the. A bunch of really smart kids at LSU that are all building this kit and now they're going on to internships and they're starting their career in ot. And another thing I really like about it is it's not a lot of talky talky and it's more, it's less talk, more walk. So like I think people are also getting into that. So they like pen testing and they like actually doing stuff which has been, you know, lacking. I think a lot of times we all see like really long PowerPoints and webinars from vendors and stuff. But I think people are really itching to do something and this is something you could do for pretty cheap and it's a lot of fun and it's all skills that people will pay money for.
99
01:04:39.000 --> 01:06:37.000
So a hundred percent and that, that's awesome folks. Like get in there, look in, look in these, in the YouTube, like follow along. There's so much that you can do. Like we're, I'm building them back here a little bit differently but same type of thing with ICS Village for some trainings that we're looking to do and, and have some OT entry level type courses that people can follow along with under the ICS Village nonprofit, you know, kind of brand doing those maybe at defcon and maybe at, you know, in other places. Not quite maybe as, as, as hands on as yours as far as building a PLC but actually interacting with a pre built PLC and, and, but it doesn't have to be super expensive like the kits, our whole goal is to have the kits. Like 500 bucks or something like that. Right? So something that somebody could get into, they can mess around with Zeke and Suricata and a firewall and understand an HMI and, you know, a little ESP32 that turns on a light or turns on a pump or does something simple. Yes. It's not something you'll see in a plant, but the concept is the same, right? It's using Open PLC, it's using Modbus, it's using DMP3. Like, it's using the same types of things that you're seeing in these spaces. I guess our point here is, is like you've got three people on the screen or in, in your ear that you're listening to. Every one of us is doing. And none of this is my job. It's not necessarily Oren's job. You know, if it is, it's like, maybe I'm getting a little bit of something here and there. But that's not the reason we do it. We do it because we want to build that next community. We want the next folks to come behind us because we see to Oren's point on the fire. We need to pass the baton. We need to pass the torch to, to the next generation of folks that are coming up behind us because eventually we're going to have to retire and who's going to be behind us to take that forward. And hopefully they're in a better place than where we came in and then we leave it better than where we found it. So that's my spiel. So thank you both for all that you're doing.
100
01:06:37.000 --> 01:06:56.000
Yeah, I was going to say thank you guys because I got the bug from the ICS village. Walking around and seeing in real life and being like, oh, that's a city
right there and there's a plc and I could just log in and tell that pump to turn on with nothing. That's crazy. And yeah, it was, it was really cool to see.
101
01:06:56.000 --> 01:06:57.000
Yeah, absolutely.
102
01:06:57.000 --> 01:08:01.000
So just really quick, my first time going to DEFCON two years ago, I was so overwhelmed with all the different villages. And when I saw the ICS be like, that's really cool. They saw the aviation village, all these other ones, the social engineering village was like, it was insane. But that just makes it more interesting. Like you're saying, Aaron, like, we gotta help next generations to, to learn this stuff, you know, get interested. And. And that's also why, like, we're getting involved doing these youth programs to get folks in the high school, others in the college to be more into the cyber security. And, and like, and then we're very also like, comment about, you know, we're getting ready to retire, like, even in the field of these companies, a lot of, a lot of people there, there, that space. OT have been there for many years that soon they will retire. Who's going to take over their, their knowledge? We need to be able to transfer that out. Need a lot of that young interest to come into this area to start learning this and take over. Because then, you know, we got a lot of new critical infrastructure that needs continual protection.
103
01:08:01.000 --> 01:08:03.000
Yeah, absolutely.
104
01:08:03.000 --> 01:08:04.000
No crawling required.
105
01:08:04.000 --> 01:08:05.000
Yeah, exactly.
106
01:08:05.000 --> 01:08:06.000
Right.
107
01:08:06.000 --> 01:08:21.000
But sometimes that's the fun part. Like we're taking an intern with us to do a client that's doing some really cool stuff like munitions destruction and things like that. So we're going to take an intern that's in college looking at cybersecurity. We're taking them to some field sites.
108
01:08:21.000 --> 01:08:22.000
Right.
109
01:08:21.000 --> 01:08:59.000
And taking them along with us and you know, put on a hard hat and safety toe shoes and let's go actually see some real stuff. Like you're going to get dirty, but that's okay. That's part of the fun. That's why I'm always smiling. It's why I have, you know, all the things that we do here. You know, I could be in it. I could be sitting at a desk and, you know, managing cloud and all that. There's nothing wrong with it. I just really enjoy this. I enjoy contributing to protecting critical infrastructure and things that are ugly and messy and loud and different. It's just, you know, I caught the bug. Kind of like what you said, Oren. Like I really just said, yeah, this is where I need to be.
110
01:08:59.000 --> 01:09:08.000
That's my favorite part. Hands down. Site visits, watching automated frozen pancakes orders and coffee cup fillers and all kinds of crazy stuff.
111
01:09:08.000 --> 01:09:09.000
Yeah.
112
01:09:09.000 --> 01:09:13.000
I met a guy once, he said if, if How It's Made isn't your favorite show, he wouldn't hire you. That's what.
113
01:09:13.000 --> 01:09:16.000
He's right. That's right.
114
01:09:16.000 --> 01:09:18.000
I want to work for that guy. That is my favorite. Exactly.
115
01:09:18.000 --> 01:09:20.000
Yeah, exactly. Or dirty jobs.
116
01:09:20.000 --> 01:09:22.000
Or dirty jobs. Yeah, that's great.
117
01:09:22.000 --> 01:09:23.000
Yeah.
118
01:09:22.000 --> 01:09:55.000
Well, awesome, guys. Well, I thank you for your time. I appreciate, you know, again, all that y' all are doing. Definitely reach out to Oren. Look at what he's doing. Look at what Ray's doing. You know, go take their classes. Go dig into the, into the content. Like there's, there's resources out there that are available. You just have to take actions. Right. So, so step in. The, the opportunity is yours and there's, there's a great career behind it, but it, it's not easy. I'm not going to pretend that it is but it it's worth it. It's really valuable important work and and it's a great community to be part of as well.
119
01:09:55.000 --> 01:10:01.000
Definitely. Definitely always reach out message away LinkedIn message away so awesome. Very happy.
120
01:10:01.000 --> 01:10:11.000
It'll be a happy day when when I see your pull request into the GitHub contributing some of your awesome stuff to make everything better for us. That's yeah exactly that's a good part
121
01:10:11.000 --> 01:10:22.000
I like so yeah for sure well awesome jets. Thank you again for joining me. Round two I appreciate it and this time it went well. Good job on the mic and and thanks for joining me today.
122
01:10:22.000 --> 01:10:24.000
Thanks appreciate it.
123
01:10:24.000 --> 01:10:26.000
Thanks for having me on also of
124
01:10:26.000 --> 01:10:41.000
course that's protected all for this week. 1 favorite A quick review on Apple or Spotify takes a minute and helps other defenders find the show. New episodes every Monday. Follow wherever you're listening. I'm Aaron Crow. Take care, stay safe and I'll see you next week.