สำเนาบทสนทนา 🔗
WEBVTT
1
00:00:00.000 --> 00:00:26.000
So that's one of the things I learned from 2025 and 2026 so far in doing these tabletops. The common thing is a lot of facilities don't know the roles and responsibilities. They're not defined. And it's largely because there's no ICS serious response plan. So it kind of all rolls into one. The other thing I noticed as well is that when the tabletops happen, it's, it's, you get that kind of definitive who does what, where, when, how, which is great. But there's also this kind of trust the bills as we talked about before.
2
00:00:26.000 --> 00:01:06.000
You're listening to Protect it all where Aaron Crow expands the conversation beyond delving into the interconnected worlds of IT and OT cybersecurity. Get ready for essential strategies and insights. Here's your host, Aaron Crow. Hey everyone, thank you for joining me on another episode of Protected all podcast. Everybody probably knows this guy Dean's been on the podcast before. You know, OG in the OT space. If you don't know him like, you must be new to this environment. So Dean, thank you for taking time and joining me again today. Excited to dig in and have more, more conversation of what goes on in the trenches.
3
00:01:06.000 --> 00:01:12.000
Excellent Aaron, thanks so much. Glad to be on here. I know this really gets to the community, so I'm all too glad to be here and thanks for having me.
4
00:01:12.000 --> 00:01:22.000
Awesome man. So those that may not know who you are, why don't you give us a very brief who you are, what your background is, history, that kind of thing just. And then we'll kind of get rolling.
5
00:01:22.000 --> 00:02:00.000
Yeah, for sure. Very very quick. I was that pale pasted guy in my parents basement hacking systems across state lines for educational purposes back in, you know, degree in computer computer science, computer security, 10 years in IT telecommunications, you know, the last 10 years in ICS and OT in water, wastewater, oil and gas and electric power. So a principal science instructor course author as well. I teach ICS515 so visibility, detection, response and a two day leadership level class on control systems as well. And in between those classes I'm in the field talking with engineers doing assessments and tabletop. So that's me.
6
00:02:00.000 --> 00:02:24.000
That's awesome. Yeah, so it's amazing. This community is so small that you know, most of us know each other but it's growing as well, which is awesome to see because the need is there. You know, 15, 20 years ago when I was in this, nobody had heard of ot like there was nobody in this ICS space. Like there was no conversation and it was all just well, I'll air gap it or I'll put a firewall in or, or whatever.
7
00:02:24.000 --> 00:02:25.000
Right.
8
00:02:25.000 --> 00:03:03.000
And I didn't need anything else. Right. And now it's really coming, unfortunately. And fortunately, in that, you know, we're seeing more and more things happening in these spaces, and
Load full transcript
everyone knows it's not a matter of if, it's a matter of when. So I, I see more and more effort and, and focus in these spaces from all those spaces, like, you know, wastewater. Those are organizations that five years ago weren't spending a whole bunch of time and effort in that, and now you're starting to see more and more of those types of organizations really focusing on it. So walk us through, like, what is some of the stuff you've been working on in those types of places and where are you seeing, you know, kind of the ball moving down the field.
9
00:03:03.000 --> 00:05:52.000
Yeah, for sure. So let's just go back a little bit to come some, some insight on your, on your point there. Like, you know, 20 years ago and 15 years ago, when I started into ICS specifically, and 22 years ago in cyber defense, like, it was, who's going to target a plc? Like, who can manipulate that? Like, they don't even know what a PLC is. Like, yeah, adversaries know what PLCs are. They have them in their labs and they target them. And they're all different kinds of vendors. So what I've seen in the field recently, and just to recap this is obviously 2026, but some of the things I'm going to draw from is 2025 experiences somewhere kind of early in 2026 is up and out in manufacturing facilities and out in. You mentioned water wastewater facilities. And I would agree that the ball is kind of rolling in the area of like, oh, we have to do something about the business, which is ot. And because there's that need now, because the Atari has been focusing on this and with impacts. So from my perspective, being in the FIELD recently, in 2026, early now, just recently out in the field doing tabletops, sitting with engineers on one side of the table and it is on the other side. And there's like a VP of engineering here and there's like, you know, CIO or CSO here. Like, the conversations that I'm having now when I facilitate these workshops are far better, far improved. And they're needed, I think, because I'm sitting there facilitating a crafted scenario that's realistic from what I've seen in the field. And it is like, wait a second, a PLC can't Take antivirus, like what adversaries techniques are they using? And so it is learning, OT is learning. We get that convergence that we hate talking about, but we know we love. Right. And so what I'm seeing in the field is more collaboration, but at a tabletop level rather than just it talk to talk to ot. It's make it practical through a tabletop. And so I love been able to do that the last number of months, specifically in the field. Now when I hear the word wastewater, we all know that that area needs additional resources. But this is not like, oh, poor them, they need resources. They're like stuck. This is like a call to action, like they can do something. And a common thing I get, Aaron, is oh, well, if we do a security assessment, there's going to be like 150 gaps that we have to, you know, how do we prioritize? And this is where
the SANS five critical controls comes in place again. And I've gone out, I've done assessments in water and I say it's all good. Like let's hold off on the 150 things you may want to consider. Let's look at the two things, two of the five right now that you can do. And I mean, yeah, if you want me, I'll reveal those two of the critical five controls that I see most impactful to water. And generally they're not doing it. And that's why we respond, that's why there's incidents, that's why there's issues. You know, so that's a little bit of the thing I've seen in the field the past few months.
10
00:05:52.000 --> 00:06:31.000
Yeah. And you know, as a, as a consultant walking into these spaces, it's really easy to go in. And I use the analogy of like my, you know, freshman English paper, when I get it back from my, from my teacher, and it's just red because everything is wrong, like capitalization and wrong words and no comma or semicolons or all the things. Like there's so much on it. It's like basically just rewrite the paper. And that's what most of these wastewater like you just talked about. Like, of course they have everything wrong. They haven't done anything, they're not up to date. So it can be overwhelming. As a consultant, I see it as my goal when I walk into these spaces is I don't want to do that. Like, yeah, I'm going to tell you all the things wrong.
11
00:06:31.000 --> 00:06:32.000
Sure.
12
00:06:31.000 --> 00:06:48.000
But I'm also going to say, okay, now put all that aside. These are the one or Two types of things that you should be working on. First, if I had one hour to spend, this is where I would spend that hour. So where are you seeing those focuses in those one or two things that you talked about in those. Out of those five critical.
13
00:06:48.000 --> 00:10:12.000
So totally love that. And the thing is, is, is you're right. I always get the kind of, it's not resistance, but it's like the overwhelming, like where do we start, dude? Like, and which ones do you think we should do? Because and, and why, like justify why this one or that one. And it's like every time it's like do an assessment, understand, meet with the engineers. Critical, meet with the engineers and then walk them through the kind of after action. And when we're walking through, it's like I just go right to it. Here's the top two, three, four, five, and here's why. And it's never because it's a nice thing to do or it's like a best practice, which is good things to do, but it's because you're in the water sector. And this is what we've seen in the water sector for the last six years, seven years, eight years, the last two years. And these are the high impacts that are going to hit you. And to counter that, here's the top two or three. So the top two things that I see in control systems in water and wastewater today is they do not have general statement, do not have proper architecture or remote access. And I'll extend it to one more control, which is visibility.
So let me back up a bit. Generally when I go into these facilities and do a tabletop for control systems, they may not even have an incident response specific response plan which is needed because it kind of kills stuff. So like the plan is. So they don't have that. And then I start with, well, let's do a tabletop and I'll prove to you with a realistic scenario that makes everything kind of like up board here realistic. And I'll prove to you the gaps that you have based on the threat. So the scenario drives us down through this facilitated workshop and tabletop and out the other end, it's oh well, you're in the water sector, guess what? Threats usually come from it into ot. That's architecture. They don't have that. And it's not necessarily a large overhaul to put proper architecture in place or at least to have a boundary to protect the OT from it and the Internet specifically as well. And I'll drop some statistics here. It's over 50% of the time that an ICS gets compromised, it's because the threat is in it and it's been allowed to transition into ot. So architecture for sure. Visibility I would think is, I know is is a really good next step, but I wouldn't do visibility unless you have sort of an extensive architecture. But it's really secure remote access because we do see threats that don't come in through it, which is still very common. The avatar doesn't have to work through it, they come in from the Internet because there's stuff out there that doesn't have multi factor authentication, doesn't have time based specific remote access with proper authentication, you know. So architecture for sure is super weak point in the sector. And I would say that remote access and I would extend that into. Once you have those solid visibility is what you need to kind of maintain an early stage threat detection kind of program. So those three of the top five ICS critical controls is what I see being very weak in the water and wastewater sectors. And this stuff is not rocket science. And it's even. This is what I love about this, Aaron, and you're probably going to see this value as well is that those controls actually help the engineering staff as well. It's not just secure to save the day. It's now the engineers with visibility as an example, they could do root cause analysis. Like they need that, you know. So yeah, it's not just security that the benefits extend into engineering as well.
14
00:10:12.000 --> 00:11:34.000
Yeah. And it's so funny you say that, right? It's most of the problems that we solve in OT are not overly complex. Like you know, you and I, I'm going to be at S4, you're probably going to be at S4 and RSA and Black Hat and all these places that there's all these vendors that have really cool, awesome products. And I was a VAR and a vendor, you know, CTO of a product company. Like all the things, right? I get it. All these products are valuable. There's needs and in the space. But when, when you're at one of these places that have nothing, right? You know, going out and finding, you know, it's, it's always, and we talk about this a lot, but it's always people process and technology, right. I can't just go buy a product and have it solve all of my problems. Somebody has to maintain it, somebody has to install it. I have to understand where my critical things are and my paths, all that kind of stuff, right? Because I, if I put, if I go buy the best Palo Alto Or Claire, you know, whatever the thing is and stick it out there. But then I'm allowing somebody in the back door, then it's not actually able even to do its job. Like you talk about remote access and I was literally at a manufacturing facility and walking it down and like, oh, we have these firewalls and we have all this and all this stuff and my. Okay, how do you do remote access? Well, I take this USB dial up thing and I plug it directly into the HMI and lean a lot of vendor and just directly the Internet. Like, oh yeah, that's, that's a bad idea.
15
00:11:34.000 --> 00:14:01.000
It's a tip that you know you're coming back to do. It's a response to help them the next week. Yeah, yeah, you're right, you're right. It's people, process and technology. I get the question all the time when I teach or when I'm in the field, it's like, so we have X number of dollars, what do we do? Do you hire somebody? And before the sentence is finished I'm like, hire a person first. Hire a person and I'll say the word AI. You know, it's not abolishing engineering, it's not abolishing cybersecurity. There's ways to adapt that after you do the foundations. But it's what I try to do is, is hire people, train people and I've hired people from it. I've hired people from OT and kind of put them into these environments and some of them succeed really, really well. So my thought would be to, yeah, you need technology for sure. And even at the ICS summit coming up in June. So I'll be there, I'll be there doing workshops. We have vendors there as well. And it's great to see the ICSOT specific vendors, but all the time first people. And what I try to do in water, wastewater, oil and gas, whatever, is when they're looking to hire someone to do the things they have to do now because forced to do these great things that are beneficial to everyone. It's. I always suggest like who do you have on the engineering side now that you can have as a champion that knows the control system and safety, you can kind of tweak their job role and have them do some tasks of cybersecurity as well for OT and that process significantly like rocket ships their program to maturity rapidly. Because the engineers, they know the control system, they know the safety, they know how the systems work and how the things that are not documented work. Right. And those people, when you think about it. Even if you're tasked with it OT tasks in the ics, those engineers, you're going to need them in its response and recovery and data collection. And data like, you know, so hiring people
back to your point critical, and then implementing one or two of those controls over time, not too long. Like these controls are foundational. Like, you know, don't take two years to be like, ah, maybe I'll, I'll do architecture now. Because that seems like a nice thing to do. Like a review of your external edge ICS firewall, a must. And a tabletop will expose those potential opportunities. And that's why I love tabletop so much, dude. Like, it's like, I don't want to sound like a broken record here, but the value, like I love seeing light bulbs go off all around the table and it gets it. And OT gets it. It's safety. Who's there? They get it. Love it, man. So much value there.
16
00:14:01.000 --> 00:15:55.000
Oh yeah, 100%. It's funny you mentioned that, you know, hiring the OT folks is. So I built a team. I was an asset owner at a power utility and built a team that we supported 40 something power plants across the state of Texas. And I had, you know, people that I hired off. Again, this was, you know, 15 years ago. So there weren't OT people, there wasn't ICS type conversations. Nobody had that on their resume. Right. So I was having to build a team from, you know, IT people and I hired people from the plants and operators and things like that. The other thing that nobody thinks or we don't talk about is when I walk into these places, I, I can walk in and I can credentialize myself because I speak the language, I look the part. I have the, the steel toe boots, I have the hard hat. It's not new, you know, I dust, I got it dirty in the parking lot before I went in. Right. You know, I looked the part because I've worked in outages, I've worked in these spaces. They can detect that. Yeah, I'm not just some person that worked in corporate and is coming down here to dictate, you know, cyber controls in their space that won't work. When you hire someone from that type of space, even if they're not a technology person, they're not a cybersecurity person, but they've been in those places. You're getting that experience. They know where the bodies are hidden, they know how the processes work. They know how to do a lotto a lockout, tag out. But the other piece to this, especially in organizations in ot, a lot of times, these people have been working there for 20 years, for 15, 20, 30 years, etc. They also have the reputation that they will. People will. The other locations will listen to them just because of who they are and because they've been in those fields, they have that trust. And then you come along with them and just because they're seated next to you and they're vouching for you in this conversation, the people across the table that normally would have given you the Heisman and not listen to you will now at least hear you out. Because that person is sitting next to you and saying, hey, just listen to him. He has something to say here.
17
00:15:55.000 --> 00:19:37.000
100%. I can't agree with you more. I think that in the tabletops or even going
into a facility, when you have that, you gain trust. So we're talking about people process technology. Like get a new tool, put it in, cool. None of that works if you don't trust. If you don't have someone that walks in there that says, I know that person, I know they know the language, they know what Modbus is and DMP3 and Profinet and like, if they don't understand how that can be abused today by the attacks that we're seeing, then what would they be doing on an hmi? Like, what would they be doing on a controller? What would they like from a safety. Let's go that way. Like from a safety perspective, why would you let anybody touch anything in the OT unless they have that respect? And so a lot of times from it, it's great because they have passion, but they're like, yeah, man, let's lock this puppy down. And they're like, give me the logs, give me the logs. I'm like, that's great, but what logs do you want? And most of the time here, not all it's generalization here, but most of the time it's give me the AD logs and give me the Windows logs. And we're good. I'm like, well, so that's about 20% of the control system. So let's kind of level up. Let's understand how control systems are actually are attacked for the last 15, dude, 15, 16 years now we're getting wow, wow. And it's like the controllers can be manipulated. We've seen that. Like the logic meets, like, you need logs from the controller that says anytime somebody touches the controller, logs into it, changes firmware, changes the logic. You need to be aware of it. Like, let's talk about what actually can. You could detect threats in the control system. Like Windows is fine and all that. So engineering workstations, of course, USB insertions, you want USB store, you want mount points too, like all those things in the registry on that device. But the engineering devices is what we see more and more being manipulated. So back to practical and back to your point about respect. When we do incident response tabletops, like I'm usually the one facilitating this from a company, ics, Defense Force, and I won't run them unless we got engineering representation in the house. Because I never want to walk away from a tabletop saying like, well, that sucked. So we always have engineers there and they bring that OT stuff. And so the scenarios we create, they're all, not all, but a lot of them are catered to the OT side based on what the client wants. But we just inject like, here's what the threats are. This is what we recommend right in your sector, in your region, your country and all that. And we build in. Well, the engineer has to get an inject that says, how do you get logs from a controller? Or the engineer has to, you know, have some ability to look at something on the firewall or something similar. So yeah, it can't be understated that or overstated that the engineers play a major role in anything in cyber for OT and that respect rightfully to them. If they say, dude, I don't trust you and don't
set up my keyboard. Yeah, man, you wouldn't want it the other way around where someone like an engineer rolls into it and they're like, can you just kind of scooch over? I'm just going to make some changes on the email security server. So it's the respect piece, right? And then it's the people process that technology. And I think you and I both go way back enough to know that building that trust, dare I say again that coffee and donuts or brisket, bourbon and barbecue is a way to do that. But aside from, you know, brisket, bourbon and barbecue, in a real life setting, the tabletop is where a lot of that relationship kind of extends and trust builds. And it sounds cheesy and corny and soft skills, but it really starts to blend. And like I joke not when I'm doing tabletops and I see that interaction, I'm like, yeah, like now that person in the sock from it, I can see it during the break of the tabletop or whatever, they connect, they're like, yeah, yeah, I need these logs too. Well, I can get you these Logs and here's where they're coming from. And like, where's your syslogs? Like, it's. It works, dude.
18
00:19:37.000 --> 00:19:38.000
And.
19
00:19:37.000 --> 00:21:30.000
And love seeing that. Yeah. So I think that's how we win. I think looking at what we've seen geopolitically, you know, with the other parts of the world currently and all that stuff recently, what happened as well in December, reported on in January, all those things, we see the geopolitical tensions. Remote access is a problem. Guess where they got remote access to terminal units. Like remote access into the devices that can, if abused and they have the access can cause damage, can cause physical damage to equipment. And so back to a tabletop. It would be shaken out of a tabletop in a scenario that's realistic in the sector to say you don't have visibility to even detect someone getting remote access into a critical asset that you have. It's an urgent device. So yeah, those controls I mentioned in the water sector that I think are lacking. I see that opportunity in some other smaller utilities as well. And it's not just water that doesn't have proper architecture. Just did a tabletop in a manufacturing facility. We did the walk down to the site first. All that stuff made the engineers high fives all around. Awesome. Was fantastic. We went in and kind of got an understanding. It thought, well, there was an air gap, but there's not an air gap. And so that learning happened. So it just makes it super practical. And I never think of a tabletop being like one and done. It's like, okay, cool, we did a check. It's okay, cool. If you want me back in six months or 12 months, let's take a look at this and see how we've improved based on the threats. Not a checkbox. It's based on the threats and looking at the data from 2025. So the SANS ICS Cybersecurity Survey, I think something like there's. I don't know the stats exactly, but there's large portions of facilities now doing tabletops and
they prefer tabletop exercises. But what I do know from the statistics in that white paper in the survey is that mature facilities are now doing tabletops more than once a year and they're recognizing the need.
20
00:21:30.000 --> 00:24:10.000
I've been touting this forever. As long as I've been talking into this microphone and before, honestly is, is those tabletops and you hit on so many real nuggets there. And I want to, I want to call them out to folks that are listening here. Like tabletops. Yes, there is a Compliance. Check the box. Reason to do a tabletop exercise as part of your incident response plan. Blah, blah, blah, blah. Awesome. That's a great thing. Everyone needs to do a tabletop. If you're at least doing one a year, that's better than none a year, right? That said, you talked about a lot of value and a lot of benefits that came out of those tabletops that have nothing to do with cybersecurity. Like when you're having. And you've got all of the team members at the table and everybody understands the perspective. Like my dad used to tell me, I grew up in the south in Texas, and my dad used to tell me, there's a reason God gave you two ears and one mouth. You should listen more than you speak. When you put people in the room and you're. And they're actually, we're all at the same table. We're all, you know, it's a, we've got, you know, food and everybody's got coffee and we don't have other, you know, distractions. And we're not enemies. We're all on the same team. And you, you're building connections, you're building that trust. And if you do it once a year, there's not enough time and opportunity for people to build relationships, right? So as the more often that you're doing those things, you're putting those people together, you're giving it. So it's a team building exercise, you're building trust. So when the shit hits the fan, excuse my language, these people know each other, right? They've already went through these scenarios. They know, they know Bob at that location. I'm going to call Bob. And it's not just some random person from the sock. Me and Bob had coffee and we sat next to each other during this tabletop exercise. Like, so we need to be looking at these tabletops. Yes, there's a cyber security perspective. Yes, it's going to help us have a more thorough incident response plan. And yes, we're going to find some things that are missing from that. We're going to find some gotchas and hey, we thought this was air gapped and it wasn't. All those things are true. And also there's so many additional benefits that are not in the, you know, the outcome or the deliverables of the, of the tabletop that are priceless. Like, we should be doing these monthly, quarterly, you know, as often as possible for all these other benefits, even if it's not bringing in you and I to do every one of them, like maybe that's too much. Maybe it's quarterly. Like but the more that you're doing these things, the more that you're strengthening your
teams and you're building this, this culture of convergence in that I'm not necessarily converging the technology, but we're one team, one mission.
21
00:24:10.000 --> 00:29:13.000
Yep, a hundred percent. So what I've seen recently, like you mentioned, like it's not even in the after action report or maybe it is, it's when the team is working together, they actually realized the roles. Like it's a common question to ask like who actually does instant response on a controller. Like and there's like people looking around the room and they're like well dude, I'm not sure. And so you're right. So once that's done, that actually speeds up recovery. Once you nail down this person is going to talk with this person or that group to get the logs required to see if the control has been manipulated. Like it sounds like a basic thing. And it's easy to understand that once that role is defined, the recovery is much quicker. So that's one of the things I learned from 2025 and 2026 so far in doing these tabletops. The common thing is a lot of facilities don't know the roles and responsibilities. They're not defined. And it's largely because there's no ICS response plan. So it kind of all rolls into one. The other thing I noticed as well is that when the tabletops happen it's, it's you get that kind of definitive who does what or when how. Which is great. But there's also this kind of trust the bills as we talked about before. So you mentioned, I guess either self facilitator or external facilitated obviously would be external facilitators to kind of would come in. So I've recognized that facilities may not be in that position yet. They want to do one internally. So I just released like kind of an artifact, I guess like a free kind of a guide that says like if you don't want to, you know, have us in cool. Here is a free list of things you want to consider to do a self facilitated instant response plan with, you know, with the OT staff and it's on the website icsdefenseforce.com so the point is, is that start something. You also mentioned a really good point Darren, about well one inch response tabletop one a year is better than none a year. So from the survey details we've seen is that again those mature facilities, you know, maybe more Oil and gas, electric and some other maturing facilities in water or whatever that are really up to, up to par. They're actually doing now tabletops, where once a quarter and these tabletops don't have to be two days long. It's like a four hour, you know, like you're, like you said, Aaron, like non distracted, kind of put the phones outside dedicated with the engineering staff or people, four hours, half day, whatever. And it's more consistent building that relationship and it's refining the roles as needed. Which was one of the major gaps I've seen in 2025 is that there's no roles defined and they don't know who's going to get logged from the controller. And yeah, so much value here. And there's other areas too. Like visibility
is one of the top technical controls. If we shift from our conversation from people and we look at the technology, when they do a tabletop and they recognize architecture, gotta have that place or I can't see what's in the network visibility and deploy that, then the benefits are not only, well, we can see the packets and the modbus, TCP and function codes being utilized, all of those things. But you can see now the abuse of those protocols getting back to what we see in the field. Adversaries continue to abuse the protocols we already have. And another thing back to the tabletop for one second is that it is like, wait a second. And they learn from the conversations, from awareness of like, wait, you're telling me that an attack on a control system is not just necessarily malware, they can just get access and reprogram the PLC with new logic from the Android workstation through an allowed port in the firewall. Whoa, whoa. So that discussion comes out too. And then that it's like. And then I'm sitting back like light bulbs are going off and then they realize, well, a technology, what technology can we deploy to detect that kind of thing? Well, visibility is a great way to do it because antivirus is not going to help you there. Right, right. And then it also learns that when there's an incident, that quote, unquote incident might not be the execution of malware, it's an adversary on a control system. Clicking buttons on the HMI or something similar. How do you detect that? Well, antivirus is not going to help you. Right. It's going to be again that visibility technology. So earlier in our discussion, water architecture for sure, remote access needs to be done in a proper way if it's required. Secure remote access, time based multi factor authentication, jump hosts all those things with tides into architecture, after those two things, you're then in a prime position to actually deploy network visibility. Because without those two things prior, or at least the architecture piece, your network visibility technology, and the person that uses that technology then is going to be far less effective. If you have architecture in place, visibility now is far more return of investment because you can understand where the protocols are, understand the different choke points you have created for containment, but also for collection of data. And that's where I see facilities really excel when it comes in and they're like, yeah, we got a great architecture network. Now let's look at the packets from this managed switch and this firewall at level three, at level two, like then I can see and I've seen this and I've helped organizations just, they leapfrog year over year and they accelerate and mature. So yeah, back to people for sure. When the people are established, the technology, it should be ICS specific, right?
22
00:29:13.000 --> 00:31:34.000
Yeah, absolutely. And as you continue down that path, you talked about the critical controls and we talked about people and we talked about tabletops and then we started getting into architecture. You know, I've got these basic things done, then I can more mature, right? And, and there's also something you said before, maybe way early in the conversation is this doesn't have to be super expensive or complex, right? You know, th, this especially to start, right? Some of this is going to be a manual lockdown with a, with a, with a clipboard and hey, where are my assets? Where, where are my switches? Where are my PLCs, like all that kind of stuff. I've literally done those with a, with a freaking camera and, and a, and a spreadsheet printed out so I can handwrite everything and IT in this room and this rack and all that kind of stuff because they had nothing. And then that's where we start. But then as you start building new stuff and you have tools and you get to a place where I've got secure remote access, I'm, I'm recording my sessions, I'm limiting access. There's dual factor authentication in that, right? All of those things. And then you start monitoring things. And that's where again, as we build on these things, it's why all this people stuff matters so much. You talked about it before. If I just started sending logs, even if I sent every log available from the PLCs, everything to an IT SOC, they wouldn't know what good or bad looks like. Like they don't know what to look for in an OT space. Like you talked about it like, it's not malware, it's not antivirus. It's more than likely none of those things. It's allowed actions in an unallowed time or way that is not going to be triggered by antivirus or other things. So those relationships that we're building there need continue so that when something comes up, we can tune these things and tell the people what to look for. And these are the types of events and are we in an outage? Are we not in an outage? What is accepted, what is allowed, what is not allowed? Like, those are the things, that's how you make this where it's actually valuable. And we're not just sending logs to send logs that are adding no value. And that's the other piece to this that I see a lot in a lot of these spaces is a CISO comes in, they want tools, they deploy tools. But the endpoint, the users, the plants, the manufacturing facilities, they get no value from it. To them, it's a cost, it's complexity, and they don't see any real value out of it. When you flip your risk, then you
23
00:31:34.000 --> 00:31:40.000
could be a risk of taking that internal information, pushing it out to a network you may not host. Hostile, that's always targeted. Yeah.
24
00:31:40.000 --> 00:32:12.000
So when I approach that, and from that perspective, when you're thinking about it from a, hey, I can't, I can't protect the world. But when I'm looking at what is the value that I can bring to the customer, Secure mode access, you hit a great one. This is going to help them do their job. It's going to help them bring vendors in securely. I can lock the
door, I can monitor the things they're doing, like all those types of things. So when we make sure that whatever we're doing where we have the intention of adding value to the customer, not just, hey, you don't know what you're doing. I'm just going to handle this. You go sit over there and I'm going to protect it for you.
25
00:32:12.000 --> 00:32:13.000
Just trust me.
26
00:32:12.000 --> 00:32:15.000
I got this. Like, no, that's never going to help.
27
00:32:15.000 --> 00:35:24.000
Right, Right. So you're bringing up really good points, so many good points, Aaron. So number one, you brought up like, you know, don't take on the world, don't bowl the ocean, whatever. So I want to talk that a little bit. I also want to talk a little bit about if you don't have all the money, what do you do with the money that you have? And like, let's, let's take a look at Water, for example, again, they're probably right now going through budget cycles to get money for piping, for water, like to push through new piping, maintain, like that's awesome needs to happen. But none of that is going to be useful if the water you're pushing through is not at the right pressure or poisoned or et cetera. So there's a cybersecurity there. So let's go back to the money aspect and like not boiling the ocean. If I look at network visibility of like packet captures in your network, a lot of people are like, whoa, that's like a lot of data. And I need, like to spend money on like a whole like array of disks to like get all that. And I get that. But wait a second. The purpose is not to be like, check, put the tool in place. It's I always take the threat approach. What have we seen the last decade plus, where do we think the adversary is going? Based on our research and based on us seeing them in the field recently. And I go back to let's look at network monitoring. Well, what devices are most targeted and simultaneously most critical in a control system, regardless of sector. HMI engineering, workstation data storing. And for various reasons, and obviously the plc, if you start with network visibility to and from those assets, which is not going to break the bank and not going to fill up a turbot hard drive in every two minutes, like it's super achievable to do that. And that data then from those critical targeted, commonly assets in most ICS facilities and sectors, we see if you have one person looking at that traffic to spot what's normal and what's abnormal. Not looking for malware as such, but looking for anomalous activity. Like that's a workable deployment of a solution with one person commonly looking at your top 2, 3, 4, 5, 10. Not gonna scale to 300 sites, but you get the idea. And if you focus on that limited subset, I'll say of network visibility, you will win, like without question. And in doing so, to your point, you're gonna show the value to engineering staff as well. So it doesn't have to be, let's boil the ocean. I think the misconception is a CISO comes in, I have to have X, Y, Z visibility check, go get visibility and so on and get everything. Another I'll say challenge I see is someone comes in and they're appointed. Now you have to do OT ICS security and they're like, let's go get visibility. And they start with the firewall between it and ot. And that's cool. There's some use cases there, there's some value and then they stop, they run out of budget or check the box. We got visibility now at the edge of the ot. That's awesome. We can determine if now we're coming in or out. Like check. The value to the engineer is not there. The value to look at the threats that we see today is not there. You have to go down into the control system. I don't want to go too deep into this, but it's basically called north south versus east west in the control system ability. So to recap, visibility does not have to be break the bank kind of solution. If you target inside east west traffic in between those devices. We talked about HMI entering workstation data storage, for example PLCs. Like that's an excellent place. High value place to start again, not going to break the bank.
28
00:35:24.000 --> 00:36:08.000
Yeah. And it goes back to all these things build on top of each other. It's a puzzle piece that all these pieces fit together. When you understand the environment, when you, when you talked about having that architecture and understanding where my critical assets are, then to your point, then I can determine which assets should I be monitoring. Because the argument that I've always had is like I've got two PLCs and environment. One of them is in the break room controlling the ice machine and the other one's controlling the turbine. They're the same firmware, they're the same everything. They have the same risk, a CVSS score. But they're not the same risk to my organization. I don't have to monitor the one in the break room for the ice machine. Yeah. The operators get pissed off, it stops working. But I don't have to spend a whole bunch of money, time and effort protecting it.
29
00:36:08.000 --> 00:36:09.000
Love that.
30
00:36:09.000 --> 00:36:14.000
It's just different. So if I understand it then it makes it easier to protect.
31
00:36:14.000 --> 00:36:31.000
So what I'm getting, Aaron, is the PLC managing and monitoring controlling the ice machine. That's dev environment. Yeah. Is that up for dev? Like you can. You want to do a pen test? Like pen test that thing? Exactly. Production. Right. Like, like that's safer. Like that's awesome. Exactly.
32
00:36:31.000 --> 00:37:52.000
But it really comes down to it's that simple. Right. And it's why it's so powerful and it doesn't have to be super expensive. If you understand your environment and you understand where the critical assets are, how connects to each other and you can't do it in a, in a vacuum. This is why it's so powerful to have it Teams and OT teams be at the same table and be able to communicate and be able to build that level of trust. Because you
don't want your OT guy to have to do firewalls and patching and all this type of stuff alone. You want him to be able to reach out to the IT team that has a dedicated firewall person. That's, that's all they do. It doesn't mean that you want them controlling your firewall, but you should at least be help. They should be advising you on your policies and making sure that it's done in an effective way and challenging the design. Again, maybe not controlling it, but at least having a dialogue. And if you build that trust, that's the type of thing that you'll benefit from as an organization. Instead of having this adversarial type relationship like this is mine. Everything from the firewall south, don't even think about it, don't look at it, don't breathe on it. It's none of your business. Which is unfortunately where some organizations are. And I think that's the biggest hurdle beyond technical, beyond, you know, cybersecurity, beyond nation state attackers. I think that is the biggest risk in many organizations.
33
00:37:52.000 --> 00:39:23.000
Yeah, I think you just nailed it a couple times there. And I think it goes back to people. And I think if you look for someone to understand the control system, the obvious answer is the engineering staff. So I'll just say it here right now, live on your shows that if someone out there is in IT and they want to do cool things and like for critical infrastructure, like come over to the OT site because we need your knowledge from it, but we need must have your like the engineering safety built on top of that. So if you're in it, you want to go to ot. I think the biggest thing right now for you as an opportunity. If you're listening to this out there, everybody is get with an engineer, talk with an engineer, take them out to lunch to understand their world because that is the business, understand how it operates, understand the control system protocols. Don't be like, yeah man, have you heard the good news of like, you shouldn't click on bad emails. Like you need to really understand the business which is the OT side. And I've seen IT folks integrate into engineering with that approach that is like, tell me how I can help you. And they're in. And they have that respect versus if they come in guns blazing, you'll never get in there. Rightfully so. And back to the people element again. If you find if an organization now, today after hearing this, this podcast, if they're looking for someone in the OT side that champion, it's going to be an engineer. They already know the engineering side, the safety aspect, conversations with the vendors, they know where the road access already is that probably didn't go through it because the vendor put it installed and installed it and it's even outside the hands of the engineer. So engineers are awesome people and you
34
00:39:23.000 --> 00:40:36.000
hit something there as well. Right? Is many times in these OT spaces, the vendors, third parties are bringing in technology, they're bringing in firewalls, they're bringing in their own systems and configuration. So it does not meet the IT baseline standards. It's probably not the same switches and firewalls and Windows machines and it's not in the same active directory and it's not patchy. Like everything is different. Right. And it's not because they necessarily want to be different. It's because many times the vendors require them to use their equipment. You only can buy their stuff, you have to use their cyber security controls and things like that. So that means that we need to really go, I know we keep harping on this, but that's where this trust keeps coming back to of we need to understand where the risks are, where the concerns are, where what the configuration looks like so that we know, okay, what does good look like, where are these things talking? What is supposed to be going on so that I can help you make sure that this is configured correctly. We're blocking it, we're locking it down and that east, west, like being able to get into the environment in a good way and see what's going on and understand that is the critical aspect in any of these spaces for sure.
35
00:40:36.000 --> 00:42:12.000
And to bring it back to the five critical controls, the people who implement the monitoring, et cetera, where do those five come from? Well, it's all threat based, it's threat informed. It's because the threats are doing this. These are at least the basic things to prevent them or at least delay them or detect them, et cetera. And so I get that a lot of the times it's, well, why the five critical controls? What's the sixth control? What's the, what's like, what's what's control? Zero. Right. Like it's, it's. Those controls exist because of the threats that we've been seeing year over year over year. And I think that they will evolve over time. I think that once the maturity level comes up in the community, it will mature. Maybe there will be a six or add an A zero. One like the first found. But I think it's going to totally depend on the threats. It's going to depend on the threats and the investment system, which can be small of people and the right technology. And I think to win is, is, is looking at the five critical controls first and seeing in water, in wastewater, in oil and gas, where we go. And if you have all the five controls done well, then awesome. It's not something I see often. And that's why we still see incidents year over year over year going back to 2025. That data indicates to us one in five ICS facilities gets compromised. And that compromise is not, oh, there's ransomware and we got it. It's a compromise such that the control system is impacted. So we're not talking Windows boxes, we're talking the control system, a shutdown, an impact to a controller, something similar. So one in five is high, man. When we're talking critical infrastructure, it's terrifying
36
00:42:12.000 --> 00:42:13.000
to think about, right?
37
00:42:12.000 --> 00:42:52.000
Yeah, there's, there's a need for IT man. Like there's a need for the protections that we're talking about. And not to sound too kind of like dramatic here, but like when we talk about convergence that happened 20 years ago, what do we do in OT security? Well, we've converged technology as 20 years ago, which means in OT security today we're defending the control system against all of the things that it has been seeing for decades. Plus the stuff, this is a dramatic part. Plus the attacks that can kill people and break gear that you can't replace overnight. Right. And that means downtime, it means brand tarnish, it means injury, possible loss of life. And. But it's only critical infrastructure after all. Right.
38
00:42:52.000 --> 00:43:24.000
And we're dealing with, you know, prime example. Again, I was an asset owner. I had 40 something power plants all across the state of Texas. If you've seen Texas on a map, it's a pretty big place. Plants were as many as, you know, eight to 10 hours apart from each other. My team was based out of Dallas, but I had, you know, plants in Odessa, I had plants in East Texas, I had plants in South Texas. I had them all over the place. Right. So my team, I had six employees and another six to 10 contractors doing various things. So I had a team of, let's say, less than 20 supporting 40 something power plants.
39
00:43:24.000 --> 00:43:25.000
Yes, right.
40
00:43:25.000 --> 00:44:04.000
And my IT counterparts had, you know, hundreds of people. You know, they had a dedicated firewall team. And my team managed absolutely every bit of technology from the boundary firewall at the site to the Control system. Including the control system. We didn't obviously the vendors controlled the control systems themselves. But we advised on the NETWORKING, the, the VMware, the patching, the monitoring, the applic, like all that kind of stuff. So we supported. My team had to understand virtualization, VMware patching, firewalls, networking, routing, like all the entire tech stack, everything that is supported in it in an OT space. And I had six guys across 40 something sites.
41
00:44:04.000 --> 00:45:55.000
There's an uneven distribution of resources on I'll again I'll bring it up the business. So hr it like finance, those departments are awesome. They're support functions, we need them. That's great. But if, if the OT part of an OT business didn't exist, HR wouldn't exist. It wouldn't exist financial like so the, the OT is the business side. So there is an uneven distribution of not only resources but an understanding of risk to the business. And boards are asking the right question. So when I teach ICS418, when I'm also teaching in June at the ICS summit coming up in Orlando, I'm teaching ICS418 there. And that's a two day leadership class class. And in that class, like leaders come there, people at the C suite come there and they realize, okay, wait a second, like you're telling me. And I'm understanding now that the control system, okay, there's a tax on that and okay, so they realign their budgets. And I am not saying take money from it. I'm saying reallocate or redistribute or create budgets for your business based on the threats we see, not just because it's a nice thing to do. I always go back to the five controls are there based on the threats we see. The threat intelligence guides us to what we should do based on what we observe consistently. Now the other side of that is the leading edge things of like how we're kind of predicting what the adversary is doing next. And we're teaching that in our classes in Sans in 5.15. I'm sharing that in my tabletops, et cetera from what I've seen. So it is evolving. These five critical controls need to be in place yesterday, yesteryear. And as we continue to grow and as threats change, there might be additionals to those controls. I can't see them being abolished by any stretch anytime soon. But in the future I think that like maybe one or two critical controls can be maybe added to that based again on the threats. And I have some scenarios of what controls to add, but I'll keep that for another podcast.
42
00:45:55.000 --> 00:46:05.000
Well, I mean, just to be frank, as we know, if you've been in the OT space, you and I have probably. I know I've walked into places that. That looks like it's the time, you know, the land, the time forgot. Right.
43
00:46:05.000 --> 00:46:06.000
It's the.
44
00:46:06.000 --> 00:46:39.000
The stuff hasn't been touched in 20 years, 25 years, 30 years. Right. And I'm not talking about nuclear power plants. I'm talking about manufacturing facilities and other places that have literally control systems that were installed 20, 30 years ago and has not been touched since. It's networked, it's running, and it's like it's very much a if it ain't broke, don't fix it perspective. And they just, it's like, you know the analogy I always give, it's like you bought a new car and you never changed your oil and your engine hasn't exploded yet.
45
00:46:39.000 --> 00:47:11.000
Which tells you something about the reliability of a lot of the industrial control systems that we actually have. They're not built to last two, three years. They're built to last decades. And there will be times when they need to be updated. We see NERC SIP mandating updates and so on and so on for integrity and safety and security. And that's great and awesome. But I mean, you know, patching is another kind of topic and issue as well that has to be done. Mature organizations now are patching basically once a year or once a quarter, depending. And it's not patch all the OT at once. It's. We do have legacy systems. Let's test on the Ice Machine PLC first. Right.
46
00:47:11.000 --> 00:47:12.000
Like it's.
47
00:47:12.000 --> 00:48:17.000
That's through. Let's look at level three responsibly. Let's look at level three or level 3.5. Patch there every six months. And then let's patch the controllers when we have maintenance window. So. So
I see a lot of the times it's like, well, we got a patch ot. Yeah, you're right. We got legacy devices. But patching OT doesn't mean just turn everything off, patch everything and bring it back up. Because bringing it back up could be two or three or four or five or ten days, right? Depending on oil and gas facility or your refinery, if you're so. Yeah. And that goes back again to the engineering staff, man. Because if they're not involved, they're not going to tell you. Well, the sequence of events to start this oil and gas facility up up is this and this and this. And we need to wait X number of hours or days for this to come back. Like, so the engineer is back to either a tabletop or even patching or changes in general. If they're not part of the conversations, then why are we having the conversations? Like, they are? Like, you know, you send a meeting out, right? It's like, well, 10 people on the list. And if the engineers say, like, I can't, or, like, you know, tentative, like, just reschedule it till they're available. Look, look, without question. Yeah, they're the.
48
00:48:17.000 --> 00:51:04.000
They're the priority. I was literally in a power plant a couple weeks ago and walking it down. It was a low site that was getting converted to medium and actually getting moved to high because, anyways, none of that matters. But we were walking it down, and there was this one section, and again, I'm the OT guy, and I've got people from the organization that are cyber. They're it. So they don't really have an understanding of power plants and things like that, that even though they work at a power company, right? So I'm the outsider coming in, but I understand the environment. So we're walking down this thing, and. And we. We need to see all the assets. So they're walking us to all the HMIs and all the different spaces, and we walk over to this one section, and it's the Ox boiler, which, if you don't know what that is, folks, it's the auxiliary bowler. Many times to start a power plant, you have to have steam getting rolling, so you. You have an auxiliary bowler that can start up by, like, generators or other smaller ways. Because if I don't have electricity, I need electricity to start. Start producing electricity. It's weird, but without going too far down that path, there was. There was an hmi, an engineering workstation that's sitting in front of. In the middle of this power plant, you know, in the basement of this space, sitting next to the Ox boiler in the dirt in the, you know, nastiness. And it was sitting there, and. And I'm having this conversation like, well, we have to protect this. Like, we need to put a cage around this, and. No, no, you can't do that. Well, it has to be because of NERC sip. I get that. Like, I understand what you're saying, but there has to be another way, because they need this to be able to start that, and if they can't start that, then the whole plant doesn't start up, and then NERC SIP doesn't matter. Right? So
we have to put, you know, understand that operational. Why is this, that? And. And in that same conversation there was the air compressors. And again folks, if you don't know at a power plant you need instrument air. They use air pressure to start tools, it runs, processes, it open valves, it closes valves. Like they, it's part of the control process. So they had two instrument air, you know, compressors. And again there was a, there was a control panel on the side of it. So because this was control and they needed both of those, those compressors to be able to run if, if one of them went down, the site went down. So they needed them both. So it became a critical control component. They're like, well we'll just build a cage around it. And I'm like, like no, you're not going to build a freaking six wall barricade around a compressor. How do you make it? How do you work on it? How do you start it up? Like again, it's not that the IT people were dumb or they were, they just don't know why that's a problem. And in their world the easy solution is just build a barricade around it. Right. And, and, but in our world we know that's not an option. So obviously I walked them through. Like instead, let's take the controller off the side of the compressor, let's move that someplace else and put it in a box we could control. And the compressor is still where it is and nobody's going to mess with it.
49
00:51:04.000 --> 00:52:59.000
Yeah, no fence needed on that asset. But that's awesome, man, that's really cool. And that's on the plant floor stuff, you know, boots on the floor. And if I look at that from a NERCSIP perspective, like nerxip. Now going all the way back to our earlier discussions, one of the controls is network visibility. So NERXIP is coming out and saying like they've like INSM they call it. So network internal security monitor, internal to the ics. So not just like your north, south, firewall, east, west conversations of the assets. And that's going to be a requirement now for like medium and high best facilities. And so that network visibility that control is not a nice to have. The benefits are coming to you because you have to have it installed. And so that force of NERCXP to protect our electric power grids is definitely the right thing because the benefits there from a cyber perspective and engineering perspective. So bring on NERC SIP 15 which is insn, so network visibility and no fences around, no cages needed for that one. But you will have to understand what your critical assets are. Your critical Cyber assets to which they deem as a device that goes down that has a disruption or impact on the control system within 15 minutes. That's a cyber asset depending on the criticality of your site, which is medium, high or low and so on. So if we go back to like kind of looking back a little bit, it's kind of higher level view. There is mandation now for these kinds of controls for very good reason. And if we look at water, well that's not there yet and it kind of sucks because they need it. And so at some point I think they will get that and I think that there's opportunity for organizations to do that at least in some way before they have to mandate to do it. And if they do it in some way before they're quote mandated to do it, they will reap the benefits before a checkbox is required. And that's important. I wouldn't wait for mandation because the adversaries are not sleeping.
50
00:52:59.000 --> 00:53:34.000
Yeah, yeah, 100%. And I think it gets back to what we've said a couple times through this is do something. It doesn't mean it has to be multimillion dollar, super complex. Do a lot of these basics you can get off the shelf. You can get open source, you can get, get, you can do a lot of this without spending, you know, a fortune in, in technology and all the things. Do the, do as much as you can with what you have and you'd be surprised how, how far you can take and, and protect and lower your risk and improve your, your perspective in, in the, in these spaces.
51
00:53:34.000 --> 00:53:55.000
Yeah. And I think that how much and what do you do? Where do you start? What's the priority? As much as you can with the five critical controls and that's where to start. I think that that's, that's the ultimate place to start. And if you need a budget, then if you run a tabletop, it actually tells you what you need because of the outcome of the tabletop and there's your budget like you, you know, there's, there's ways to justify that stuff.
52
00:53:55.000 --> 00:54:05.000
So what do you see come up over the horizon? What are some of the things that, you know, maybe one thing, at least one thing that's concerning and one thing that, that you see is promising in this space.
53
00:54:05.000 --> 00:55:25.000
Yeah, for sure. So I think the concerns for me is really around how the adversaries continue to manipulate the control system devices using parts of the control system against itself. So we call that living off the land. So we see more and more of that and the concern is that that stuff's hard to detect if you don't have network visibility. With it, you can baseline understand where there's anomalous activity with engineering focus. Without it, it's like well, the controller did something and now we have, you know, production down that already happened period, full stop. It's proactive versus reactive. So my concern is not knowing what's happening inside the internal network of the control system down at East West. From a positive perspective, I have seen organizations so like 57% of organizations surveyed right now have an ICS incident response plan. However, not sure that's a plan that's actually been executed and exercised with threat informed scenario sector specific, at least annually. Right. So the positive is that we are seeing organizations say, you know what, an IT incident response plan will only help us out 20% of the time in ICS and OT. So we gotta have a dedicated plan
and just again that's positive that they're now having that plan. 57 plus percent. But my question then is tinfoil hat on. Is. Is. Is are they executing it? Are they exercising that ICSOT plan in a tabletop or did they create it
54
00:55:25.000 --> 00:55:31.000
once and it gets stuck on the shelf and collects dust and nobody reads it and nobody or people forget it's even there?
55
00:55:31.000 --> 00:56:04.000
Yeah. Or did they let AI create it and then they're screw it anyway? Like you have to have an engineering knowledge. Yeah, yeah. We have to have that in there. AI will help later on at some point. And there's even cases where I got to say it. There's even cases where AI can help engineering as well, troubleshooting, et cetera. But making it do things today, action things inside the ics. I would be very hesitant to have that happen today in many critical. There's so many other things we can do that have so much higher value now AI can. We can do that when we get, you know, the basics done. Yeah. The foundational file controls first 100%.
56
00:56:04.000 --> 00:56:07.000
Yeah. AI is not going to be. It's not going to solve world hunger yet.
57
00:56:07.000 --> 00:56:13.000
We can try. So on the Ice Machine plc. Yeah, put it in the Ice Machine plc.
58
00:56:13.000 --> 00:56:16.000
Exactly. We should all store our Ice Machine plc.
59
00:56:16.000 --> 00:56:19.000
Love your ice machine. It's great.
60
00:56:19.000 --> 00:56:25.000
So what's call to action? How do people find more? Take a class. Where are you going to be speaking? All the good, all the good stuff for sure.
61
00:56:25.000 --> 00:57:32.000
So LinkedIn is like continue to post things on LinkedIn right now, which is like ICS related. Ot related. Like free things, like kind of things to help help people Build tabletops, all those kinds of things. I do tabletops, I do assessments in June. I'm really looking forward to June. I'm putting a lot of effort into a hands on workshop I'm doing in June at the ICS summit sans ICS summit in Orlando and I'm going to be teaching there as well. ICS 14. So for leaders, two day class packed class. Like there's two days of content but it's really three days of content in two days. Like it's going to be an awesome ride. So that's the kind of leadership level class but I also teach ICS515 and I teach that at least kind of like once a month and it is global. I'm in Orlando in March, I'm like across the sea. Like you know after that I just came back from London like all over and 5:15 is a six day class and that goes into network visibility, it goes into incident response where we look at living off the line capabilities of Yavsuri, how to detect that stuff, nation states and all. And yes we talk about AI and ransomware as well. We focus on the engineering side and that that's exactly what I think we continue to need.
62
00:57:32.000 --> 00:58:33.000
That's awesome. Yeah guys, if, if you haven't been to a sans course, if you haven't checked those things out, you absolutely need to. It's a great time. Great. There's so much value there. I would send, you know, when I, when I was at another consulting firm, even when I was at, at the ass, you know, when I was an asset owner, I I sent folks to those classes especially if you have it people that are getting into ot, they don't really understand it or even those OT people that have great knowledge in the control system and the operational side but they don't necessarily understand it's that great. It's really a great convergence place to be and really understanding the whys around these things beyond just. It's. There's a lot of how in it as well but there's a lot of why. Why are we doing these things? Why do we care about this stuff and why is it important to really focus in these areas and those five critical controls like you talk about. That's awesome man. Well, thanks for the time today. I'm excited to see that and be part of that. I'm actually trying to get to Orlando this year. It's been a minute since I' so hopefully we'll, we'll see you there. And thanks again for your time today and keep keep fighting the fight, man.
63
00:58:33.000 --> 00:58:37.000
Awesome. Aaron, thank you so much man. I appreciate it. All the best. Absolutely.
64
00:58:37.000 --> 00:59:02.000
Thanks for joining us on Protect it all, where we explore the crossroads of IT and OT cybersecurity. Remember to subscribe wherever you get your podcasts to stay ahead in this ever evolving field. Until next time, Sam.