رونوشت 🔗
WEBVTT
1
00:00:00.000 --> 00:00:25.000
We've talked about, probably ad nauseam, you know, the IT technologies wonderfully well suited for the IT environment. Not as well suited for the OT environment when safety and reliability are the number one and number two considerations. And so again, it's been exciting to position a product that specifically reflects those unique challenges.
2
00:00:25.000 --> 00:00:43.000
You're listening to Protect it all, where Aaron Crowe expands the conversation beyond just OT delving into the interconnected worlds of IT and OT cybersecurity. Get ready for essential strategies and insights. Here's your host, Aaron Crowe.
3
00:00:43.000 --> 00:01:25.000
Hey, everyone. Thank you for joining me for another episode of the Protected all podcast. New Year sickness, cancellations, all the things. So we're a little late on this one this week. So, Steve, thank you for taking time. Steve and I have known each other for quite a while. Everybody in this OT space, if you've been around OT anything like that, it's a fairly small group. So we've seen each other wearing different hats in different places. Whether I was at EY or I was an industrial defender, I was at these different places. But these conferences and these people are small, so we all interact and we know each other. So, Steve, thank you for joining me. Thank you for taking the time. Why don't you introduce yourself, tell everybody who you are a little bit about your history, your background, etc, and how you got into this OT thing and then kind of what you're doing now.
4
00:01:25.000 --> 00:03:28.000
Yeah, well, it's great to be here. Thanks so much for having me, Aaron. You know, we've been talking about doing this for a little while. I'm glad that we were able to make the connection. And, you know, we've had some interesting things happening on the product side. So I hope that we've got some interesting things for your audience to talk about. But, you know, my name is Steve Rutherford. I'm the VP of Sales for Hyperport. We're a secure user access platform for ot. My background context is I was a military officer, an army aviator, serve my time and, you know, protecting the nation's critical infrastructure as a whole in that capacity. I'm proud of what I did in that role as I transition out of the military. You know, really looking to see where would be a good fit for me. Right. It's always an interesting time when you're transitioning because it's a whole new, completely different world. So I, you know, went and talked to a lot of folks, you know, did a lot of different interviews in a lot of different industries and, you know, found operational technology specifically on the OEM side initially. Right on the OEM manufacturing side was really closely aligned with a commercial version of a military mission. Right. OT operation technology, running the infrastructure that powers our day to day lives here and where the safety and reliability and maintenance of all of that is of the utmost importance to the nation, was a great mission. And then the folks that worked in OT were very similar to myself in terms of our, you know, our background and experience and personality. Very pragmatic folks. Really focused on delivering great value and tight constraints sometimes. So I loved it. I thought this would be a great opportunity and moved into OT cyber. You know, I've been in the, the space here again. We've introduced over four, five, six years ago now and currently with Hyperport and excited to, you know, be out in the market, seeing it evolve, seeing the different things change.
5
00:03:28.000 --> 00:04:51.000
That's awesome. Yeah. You know, I talked to so many and you're right, a lot of the folks that sit on my podcast or you know, that we just talk to in general, there's a lot of, a lot of veterans and I think a lot of that comes from that, that similar kind of theme. And protection. Right. You know, my podcast, Protect It. All. Right. The whole, the whole theme around it is, you know, I've got OT and it kind of highlighted in there. It started out, I really focused on ot. I've opened it up to more in IT and ot, just cyber security thing. But the whole point is protection. Right. And that doesn't always mean defense. A good offense is also protection, as we know, from both military as well as in cyber. But you know, that mindset really helps us in this OT space because OT is just different than IT and just that mindset and how we approach things and the problems that we solve and how we solve them and you know, the responses that we have, it can be the same technology, but we respond to it a little differently. So, you know, I do see a lot of veterans. Not that there aren't veterans in the IT space. I absolutely see them over there as well. But I definitely see that mindset here and being a big benefit. So. So how did that transition go? And then kind of, how did you get into, you know, going from the OEM side and into, you know, a product and because I've been in all. I've been a cyber, I've been an, you know, an asset owner and I've been a vendor, I've been a consultant, I've been all those things. They're different roles.
6
00:04:51.000 --> 00:04:52.000
Sure.
7
00:04:52.000 --> 00:04:55.000
Solving the, the same problem from different directions, different angles.
8
00:04:55.000 --> 00:07:22.000
Yeah. So the cyber Considerations of OT have been known for quite some time. The emphasis on solving those cyber problems continues to grow, I think, in adoption every year. And so I kind of recognize that that was a growing opportunity to really be able to go out and try new things and see new technologies and new applications of technology to problems. And that excites me. Right. I really enjoy variation and diversity and learning new things. So I said, hey, that, that cyber thing with no T is really exciting. So let me go check that out. And from a product perspective, you know, the kind of companies that I have
Load full transcript
deliberately sought to work for are those companies that have a product that can meaningfully add value to the OT operator, right. To the OT organization to help them do their job, you know, more effectively, more cost efficiently, more securely. And so I've kind of gravitated to companies that I think fit that bill. And so remote access has been where I've kind of landed here the last four or five years now, specifically that kind of subcomponent of OT cyber. And it's exciting to see, right. When you look at the adoption of technology seven years ago, it was very much around intrusion detection and still remains, to some degree, intrusion detection. Right. There's a technology adoption curve for everything. And different companies go through that, that. That curve at different points, I think very early majority, right. You know, it's been over the last, you know, three or four years. And so remote access has kind of followed that same path in terms of adoption. Everybody that needed access happened during COVID right? If you needed remote access, you put in a, you know, a mechanism to provide remote access. Now, was that mechanism, was that tool the best tool looking back, right? With maybe, maybe not, but everybody that needed access got access. And so it's exciting to see those companies that have, you know, had the time and the space to experience and understand the different challenges around access and the different capabilities on the product side. To start say, hey, you know, we've got a solution, but let's. Let's maybe look for something a little bit better.
9
00:07:22.000 --> 00:07:23.000
Right.
10
00:07:22.000 --> 00:07:27.000
A little bit more modern. Right. Technology is moving at a great pace, so it's exciting to be part of that.
11
00:07:27.000 --> 00:09:15.000
Yeah. You know, being an asset owner, I started this, you know, a long time ago. And, you know, I had a team of people, we were headquartered in Dallas, and we had power plants all over the state. And if I wanted to do anything at those plants, I was picking up the phone and calling somebody locally, or one of my guys was getting in their vehicle and they were driving to site there was only so much that we were allowed to do remotely and only had access. And I was a very advanced architecture. Like I had secure remote access capabilities in these spaces before most other pro people probably did. But for the most part, most of my sites were very much a, you will not be in my system unless you're standing in front of the system. Right. That was a very hard and fast rule. And to your point, it kind of adopted again, some fast learners like me was really able to drive it and push that type of thing. But even then, even though the technology and the capability was there, there was still a hesitation to allow very many people access. And Covid changed that. Right. Covid said, you can't come to site. I still need this site to work. We have to be able to do remote access. And it flipped the script to the point of just make it work. It doesn't have to be good or best. It just needs to happen. And then we're now backtracking into, okay, we have this remote access. Are we doing it the right way? Are we secure? Is this the best way to do it? They didn't know that answer. They just made it work. And now we're. Yeah, we're finding more and more products like yours that it's not like remote access is a new non concept. Right. This is technology. It's been around a long time. But the specific needs and capabilities in OT are vastly different than what they are in it, which is why products like Hyperport are important. Because the problems you're trying to solve are the same and different at the same time.
12
00:09:15.000 --> 00:10:28.000
Yeah. It was a forcing function that drove what I think holistically is a conservative organization. Right. If we look at OT as a whole. Right. Generally conservative by, you know, total necessity. Right. You, you can't be disruptive when you've got things that explode. Right. And kill people. That really forced everyone to get comfortable to a certain extent with access. Now the threat landscape, I think, took advantage of that. And we've learned some hard lessons about, you know, why there was that understandable hesitancy there that now again, the technology has shifted. And we've learned from our adversaries, we've learned from the organizations that need this access. Like, what does write look like for you specific to the context of your operational environment? Right. Because again, like, like we've talked about probably ad nauseam, you know, the IT technologies wonderfully well suited for the IT environment. Not as well suited for the OT environment, when safety and reliability are the number one and number two considerations. And so again, it's been exciting to position a product that specifically reflects those unique challenges.
13
00:10:28.000 --> 00:11:02.000
What are some of the things. So obviously we've talked around big picture of, you know, remote access, why it's important, why, you know, kind of what some of those driving factors that have fast tracked it in the OT space, which I think was going to happen eventually, but obviously Covid, you know, kind of hit the accelerator on that. What are some of the things that you've seen in the industry, the differences around OT's secure mode access in these spaces, dealing with old systems, dealing with, you know, lack of, you know, the complexity and, or not complexity, but, you know, maybe maturity in these spaces. Right.
14
00:11:02.000 --> 00:13:43.000
I think complexity is accurate. Right. So these organizations have grown through acquisitions and divestitures. Right. With different maturities from an architectural perspective, from a technology perspective. So you can look at the market and 80% of it, if we're critical infrastructure, DHS defined critical infrastructure. 80% of those environments, you could cookie cutter say,
yeah, if I understand water and wastewater, I understand power generation, I understand manufacturing, it's the 20% that are uniquely and excitingly different in each of those verticals because there is a diversity of the equipment. Right. The operating systems. Right. New and old, the OEMs, the different kinds of equipment. Again, we know the classic operating system that's been running, you know, for 10 years, unpatched by necessity because it has to run a critical process that you're afraid to take offline. So, you know, the ability to accommodate a non standard. Right. A non homogeneous environment is something. I think that one of the reasons why I don't think IT tools have gained the adoption on the OT side that they could have because you really have to be able to accommodate quite a bit of diversity in what looks like a homogeneous environment, if you look from the OT side. So you combine that with the fact that you can't introduce clients and agents and disruptive or potentially disruptive components of a solution into that OT environment, that cuts out another 80% of what are the classic IT technologies that just don't work. Right. But I think it's interesting you're talking about large trends and I'd be interested to hear your thoughts on this. Five years ago, it was very much a message of convergence. We heard this message of IT OT convergence. Let's make it work. You gotta figure out how to make it work. We're spending all this money, we've got all these great tools on it. Ot, let's bring you into the future, bring these networks together. I have seen in the last couple of years, I think a start to move back away from that perspective to a diverged network. Like, hey, we tried to do that, that convergence with varying mixed degrees of success. And now we've decided that we would rather diverge because the considerations of each environment are sufficiently great that we can justify the investment for a technology that's appropriate for each of those environments. I would be curious to see your experience in, in that kind of, kind of big picture.
15
00:13:43.000 --> 00:15:43.000
Yeah, I've seen both sides of that. I've seen it implemented as well as could be done. You know, I think there is naturally some convergence in some things. You know, let's say switching in firewalls, right? There's no reason why the firewall team can't manage the firewalls at an OT site. But the divergence is they should be dedicated OT firewalls. They should be handled with dedicated OT policies. They should have different SLAs, they should have different expectations around making changes. Like, you're not pushing those things. You're not making changes on Friday night at midnight because that's your IT outage window. An OT site doesn't have an outage window. A power plant runs 247 because you want your lights and electricity and heat to work all the time, right? So you can't just go off of those same. So that's where. That's the difficulty. Right? And unfortunately, like with many things, is sometimes the pendulum swings too far one way or the other. You know, it doesn't have to be all or nothing. It can be somewhere in the middle where it says, hey, this team has a lot of experience and they have. We have a dedicated team of firewall engineers that. That's all they do. Like, they're really good at designing firewalls, looking at configurations, setting policies, understanding trends, understanding all of that type of stuff. I shouldn't have a local site OT guy that doesn't have all that experience and time to be looking at those things. How about I just make him the approver? But I've got an entire team of firewall people that can manage it. Like my team back in the day, I had a team of six people. I mentioned this before, right? And my guys had to be firewall people and switch people and they had to maintain VMware and they had to maintain active directory and patching and backups, and they had to be, you know, an inch deep and a mile wide. Like they, they didn't have time to be an expert in any of those Things on the IT side, there's a dedicated firewall team, a dedicated VMware team, a dedicated networking team. Like all these different things.
16
00:15:43.000 --> 00:15:44.000
Yeah.
17
00:15:44.000 --> 00:16:08.000
So my piece to this convergence was I want these teams to help to be able to be Tier 3 support, to be able to be driving some of these things. But the ownership still lives in the plants and in the OT space because it has to. And I think that that blend can be successful. But if you just try to push IT products and teams down in the OT space, that's where bad things happen.
18
00:16:08.000 --> 00:17:20.000
Yeah. The authority has to match the responsibility. And when you have a solution that bridges potentially. Right. If we want to talk technical from an architecture perspective, we have technology that sits at the Enterprise DMZ in 3.5 that has connectivity, or at least potential connectivity and visibility from the IT and cyber side that also provides controls into the OT environment. You really have to be mindful of that exact consideration that you can still maintain monitoring and visibility and governance and oversight at the IT cyber higher level, but you have to enable the operational side to make those decentralized autonomous decisions around. Again, when we're talking access, hey, who should be my environment? When should they be in my environment? Can I validate that they are who they say they are and that what they need to connect to is safe and effective? That's really, really important when you start to blend. Right. Even at a, you know, a technical or higher level, you have to be able to, to make those, those kind of policy enforcement, policy enablement decisions from a technology perspective.
19
00:17:20.000 --> 00:19:43.000
Yeah. And when you get into the, the meat and potatoes of many of the OT spaces, we hit on it a minute ago. There's high levels of, in
these environments, but there's not always high levels of maturity. So what I mean by that is I may have Active Directory, I may have firewalls, I may have VMware, I may have all of these things living in an OT space, but they're not going to be to the same maturity and configuration and interoperability that you would see the same types of system in an IT space. Right. They're going to be very basic level policies, group policies are going to be very basic. You know, you know, all of those things are going to be at a very entry level, out of the box, scratch the surface type capability, which is where a lot of the problems begin, especially when you start bringing these, you know, if you were going to try to converge really complex GPOs from an IT space into these OT spaces, which is why products like Hyperport that offer capabilities like Authentication, all those types of things. Because in these OT spaces I don't need the necessarily complexity and maturity that I do in an IT space. I don't have a bunch of people installing things. It shouldn't be going to the Internet, I shouldn't be browsing tick tock, I shouldn't be doing all these things. So when I scrape off all of those requirements and say I just need a really old system to be able to authenticate with something outside of itself and to be able to, you know, make sure the person that's logging in should be able to log in and have some level of credentials, some level of, you know, ability to lock them down to either just this device or hey, even on this device, what they can do on this device. That's the thing that we have not been able to do in an OT space across the board. Because not all devices can join Active Directory, not all devices. You know, I can't install, you know, agents and widgets on these things. I can't a lot of times modify the configurations on them. So I'm really hamstrung on how I can really lock down these environments because they just don't have. Not to mention that I don't have a support staff that can run and modify, test and do all these things in these spaces. So a lot of times it's just like, well, we just won't do anything. Like I'll just have local logins because that's all I know will work. That's all I'm comfortable with.
20
00:19:43.000 --> 00:19:44.000
Yeah, you go ahead.
21
00:19:44.000 --> 00:19:48.000
No, I was going to say. So how have you guys dug into that? What do you see in that?
22
00:19:48.000 --> 00:24:06.000
Yeah, so I think if I look at ot specific remote access, right? And there's some great companies in this space outside of Hyperport that are trying to solve that problem. There are certain capabilities that have received enough adoption specifically from a compliance perspective, right? That's been a forcing function around specific capabilities that are now table stakes, right? To be a vendor in this space, like you have to be able to do multi factor, right? You have to enforce multi factor authentication. You have to be able to monitor a user session. You have to be able to, you know, time based approve access into an environment. And a lot of those come from, you know, things like SIP, right? 3, 9 around electronic remote vendor access into your environment. That's table stakes, right? All of the technologies and say Hyperport up until recently focused on static permissions to enable user access, right? And static permissions being. Once I have trusted you as a user Aaron, right. I've provisioned an account. I've given you role based access to a certain subsection of the systems in my environment. I've enforced multi factor authentication on you. I trust you. Right? Now, when you rely on those static permissions, they become a liability because the nature of the user, right? As they interact with the systems, as they interact with things outside of the system, right? This is where our adversaries are trying to stay a step ahead of us, right? Those users may be influencing their session with malware, ransomware that they may know or not know after their provision, you know, their account's been provisioned, et cetera. So when you rely on those static permissions, it becomes reactive, right? The organization has to react to changing conditions. And you highlighted some of the difficulties when you have a reactive procedure. It's because the OT folks are wearing multiple hats, right? You don't have the dedicated resources that you would have on the IT team to have four, five, six different functions that will allow you to be as proactively reactive as possible, if that makes sense. So we've done with Hyperport, you know, recently is really tried to shift the model from static permissions to dynamic active permissions. And so what that means is we've generated and what we call a trust engine that utilizes AI and ML to take trust signals, right? We've got a couple dozen trust signals that we pull into an algorithm that essentially identifies how trustworthy a user's session is over time, right? So not just only at login, but also as they interact with the system, you know, what's their device posture, what are the, you know, the characteristics of their browser, their IP address, their hardware, their time of login, right? What are their historical times of login, what are the systems that they typically interact with, right? What are the typical data transfer patterns of that user? And take all of those factors into consideration to generate a trust score, which is a reflection of a user at a point in time. But again, that changes based on, you know, on that user's behavior as they interact with the system. So we combined that trust engine with a policy based access control engine that allows us to enable organizations to make decisions for different kinds of users based on a level of trust. And so I can give some examples of that if that's interesting about the AI trust engine, right? The trust score combined with the policy based access control, right? How those might
interact with each other in an organization.
23
00:24:06.000 --> 00:26:02.000
You know, the interesting thing with, to your point, and you, you talked, there's a lot of great nuggets in there. Right. The bigger problem that we have in the way that we've done remote access or granting people access in the past you said is like, hey, I check your, you've got a key to the front door. And I just assume that you've gotten the front door so you can do anything you want inside the house. Like, I'm not monitoring you, I'm not watching you. You can walk in, you can cook, you can open the refrigerator, you can go into my bedroom, you know, you could go my closet. All those types of things. Right. In an OT space that can obviously be a concern. We like segmentation, we like our, you know, segmenting off my boiler away from my turbine and away from my third party controls. And you know, if I'm letting in a vendor, if I'm laying in a plumber, I want him to go work on the plumbing. I don't want him in my electrical panel, right. So that, that's where this trust and you know, just the basic level, not even getting into the AI and you know, the vulnerability side of things, just the basic level of, of. I want to make sure that when I'm giving somebody access that they only have access to things I want them to have. And on those things, they can only do the things I want them to do. I've approved them to do these. So in ot, we do this a lot. Lockout, tag out, lottos, sure. You're going to go and work on this circuit, we're going to lock that circuit out. Everybody knows you're working on that circuit. And if you're going to work on something else, you need to come back here, let us know and we'll lock that thing out. Right. So we have that understanding and concept in these OT spaces is we want to be able to do that in a digital way, right. So we want to lock them down. But then you start talking about session recording. I can't tell you how many times. And I'm not going to name OEM vendors by name. Everybody knows who I'm talking about. Those OEM vendors remote in to make a change or they're doing their normal maintenance, something happens and now something starts working that wasn't working or stops working that was working. And the vendor's like, well, I didn't make any changes, I didn't do anything. It wasn't us. I don't know why it's doing it. Right. You're like, like what did you do? We didn't do anything.
24
00:26:02.000 --> 00:26:04.000
Okay. Yeah.
25
00:26:04.000 --> 00:26:11.000
Having the ability to record that and Understand that. Go back to logs, see what was changed, see who did what, whose hand was in the cookie jar, all those types of things.
26
00:26:11.000 --> 00:26:12.000
Absolutely. Yeah.
27
00:26:12.000 --> 00:27:18.000
And then lastly, the whole vulnerability side of this, because we know in OT we have these antiquated. Antiquated may not be the right answer, but many times it is really old systems that many times can't be patched. Or even
if they can be patched, we're not patching them because it's too big of a risk many times to patch them because it breaks something else. It's usually less of a risk. If I do the risk reward factor, it's usually less of a risk to just let it ride than it is to update it. Especially now. Now maybe I'll do it in an outage window in the fall when the unit's offline, all that kind of stuff. So having the ability to understand what those risks are, those vulnerabilities are, and to mitigate those things other ways, other than just patching is vastly valuable. It's valuable in it, but it is hugely valuable in OT because of the fact that we aren't able to patch. And many times in my organizations, I don't know, I just know because, like, if I just do a vulnerability assessment on an OT space, it's just all red. It's like your, you know, ninth grade English, you know, report that just everything is wrong. It's just red.
28
00:27:18.000 --> 00:27:20.000
Red.
29
00:27:20.000 --> 00:28:21.000
That's unhelpful. Like everything's bad. Like, what was good? What did I do? Well, like, I can't. It's really easy to go into that as a consultant, to say, this is where I'm excited about AI to start plugging into these things, to say, okay, we know all of these things. We can. We know we can't patch this stuff. What is my risk in these spaces? The risk and the analogy I always give is I've got two PLCs. They're the exact same PLC, PLC, whatever make, model you want to say. One's controlling the turbine and the other one's controlling the ice machine in the break room. They both have the same firmware. They both have the same risk and the same vulnerabilities. But one is not a big risk to my environment. Right. As an organization. If the ice machine goes down, operator is going to be pissed off. But I can still run my plant if the turbine goes down. Whole different set of risks. So that's where the risk is different. Even though the vulnerabilities, the CVE score is the same, the risk to My organization and understanding of that is vastly different. And that's where this.
30
00:28:21.000 --> 00:28:22.000
Yeah.
31
00:28:21.000 --> 00:28:25.000
Complexity comes into this mathematics of what is a real risk.
32
00:28:25.000 --> 00:29:42.000
It's a good example that we have taken and applied to user access. Right. It's essentially what are the risks and vulnerabilities associated with individual users. Right. And so if you look at those capabilities that you described, the ability to record, the ability to segment access, the ability to, you know, put somebody in a weight room and allow them into your environment only when you validated. Right. That again, I think that's all table stakes. People expect that now, by nature of the way that we've been doing this. And what's changed, to use your analogy earlier, is when I invite a plumber to my house, I can give that plumber access with a specific key to a specific room. But if I'm not at the house, Right. How do I know that that plumber that I scheduled to come in and do that work is the plumber and not somebody else? Right. And that when they get into the, you know, the plumbing cabinet, that they don't start trying to go through the sidewall, you know, and dig into something and, you know, cause, you know, additional work to be done. We're trying to apply that same kind of understanding in an. In a way that alleviates a human having to get in the way is not Right.
33
00:29:42.000 --> 00:29:43.000
Right.
34
00:29:42.000 --> 00:31:00.000
We want humans to be in the loop, but we don't want them to be forced to spend all this time and energy around managing. Right. In addition to all the other tasks that they have to accomplish managing those specific access components. Hey, is this is Steve? Is he here? Is he. Right. Got the right credentials. All right. Is access approved? So we've really tried to be very mindful to give operators visibility of what those policies are. Right. So I was going to give an example earlier around, when you take a trust score and combine that with the policy, what does that mean for an operator? So that means if I'm an internal employee and I provision access for my employees to a certain system, I can say, hey, when your trust score, right. When all of these different characteristics combine to provide a trust score that is highly credible. Right. High trust, I'll allow you to connect on demand. But Aaron, you're a vendor, right. To that same system, if I want to give you access to that, you need to be high. And even if you are high, I want to be able to automatically place you into a moderated approval workflow process. Right? Easy. But if you're a low. Aaron. Right. If you Transition to a low while you're connected to my system.
35
00:31:00.000 --> 00:31:01.000
Right.
36
00:31:00.000 --> 00:32:00.000
You do something that causes us to go, whoa, there are. Things are not right with Aaron. I need to be able to automatically say, hey, let's put Aaron in a quarantine. Right. Let's disable the access for the moment, put in Aaron into the quarantine and validate that everything is still safe. Right? Nothing. Aaron wasn't hacked. Right. There's not a malicious actor that's now in my environment that's hijacked his session. You have to be able to do that in real time instead of reacting to something that happened after the fact that vendor went in and changed something. Who did it? I don't know. Let's look at the video. I still have to react. I still have to go in and investigate. Right. After something's happened and it's really around. How do we prevent and prevents a tough sell sometimes? Right. Just like it is trying to convince you to go to the doctor, you know, before you have a problem. Everybody wants to go to the doctor when they already have a problem. But we really want to give organizations the ability to prevent those kind of problems from ever being, you know, impactful. Right. To those systems that are driving their business.
37
00:32:00.000 --> 00:34:42.000
Yeah, dude. And that. That is so huge. And we talk about this in the OT space and our operators, our asset owners are hesitant because they've been burned by promises from it. This is what excites me about this approach, is that it's not intrusive. I'm not having to install new things. I'm having to redesign networks. I'm not having to change their business process. They're able to give access. They're able to do the things they need to do. And it's more focused on, you know, I'm not stopping the main. The plant still runs. I just made Aaron sit in the sidelines until somebody watches what he's doing. Right. It's not like my plant's still running. The PLCs are going, the turbines running, you know, the things are doing what they're supposed to be doing. But this outsider that was wanting in it was knocking at the door. You've made him pause over there. And I don't have to take an operator away from his normal job to sit there and watch the screen as this guy's clicking, as I'm surfing on Instagram or whatever, because I'm not really paying attention because I'm bored and it's boring to watch somebody else work on the screen. And I'm not Even there, I'm just like, whatever this guy's doing, I've seen this a thousand times. So I'm just not paying attention. How can I expect anyone to pay attention to that? It's impossible for a human to pay that much unless there's like, like the sky's falling, you know, I've got 10 people, we're all watching the screen because that's the only thing that's going to make us work. Right? Like, but nine times out of 10, that's not the situation. The guy's coming in for maintenance, I let him in, maybe I've got the screen up, I'm half ass paying attention to it, maybe not even that much. And then it's not until to your point, something bad happens, you know, boom. The incident happens. Now I'm right of boom, trying to respond to what happened, what caused that thing, instead of to your point, we all want to get to a place where we're left of boom. And we're preventing that boom from happening. And we're able to try to say, hey, wait, wait, wait, wait, before you click that button, you know, there, there's very simple things like, hey, you know, going back to my Cisco days, you can log into the switch and I, you can do show commands, but you can't enter configuration modes and start changing configurations. Like, I'll allow you to look at what's there. I don't want you to make changes on the fly. Right? You're not approved to make changes, so those commands are not even available to you because I don't want you to make changes to my configuration. That takes another process and we have to get the change order. I want you to be on site to do that, or I want to have somebody on site. I want to review your work. Like there's all these things and this is the business process that ot really understands and likes. And that's why I think that approach works so well in this space.
38
00:34:42.000 --> 00:35:58.000
Yeah, it's about being able to allow the organization to layer on the appropriate controls to give access in a way that that organization wants to deliver access without requiring a large cumbersome administrative and technical overhead to achieve that outcome. Right. And you mentioned one thing that I did want to address. Right. You know, it's great. AI ML technology is wonderful. They're great capabilities. There's also a lot of understandable concern. Right. And so when we developed these capabilities, we were extremely mindful of the sensitivity of the environments and the data. And so what we able to accomplish was essentially generating these Trust signals, utilizing those algorithms completely on prem. Right. With no cloud dependencies, with no external connectivity so that all of that data remains within that OT environment. Right. There's no external connectivity, no influence or visibility. Right. I think that's a very important and understandable concern and I just wanted to make sure that that was really clear because we wanted to, to really be mindful of that in organizations where that's a consideration.
39
00:35:58.000 --> 00:36:21.000
Yeah. And I think many OT spaces are going to need that, whether it be from a regulatory requirement like in a NERC SIP environment in our power utility spaces, or even just a comfort level of, hey, I really don't want unfettered access into my, into my OT spaces. I'm okay with using the tools and the capability, but I don't want it going to Google. Right.
40
00:36:21.000 --> 00:36:22.000
I don't want to, I don't want
41
00:36:22.000 --> 00:37:30.000
to have a connection from IoT Network to the Internet. Like that's jumping way too many bridges. But if I can do all those things locally and I have those capabilities, is it the same? No, of course you're going to have more compute power in the Internet than you are in on my local prim. It's not the same, but I don't need that level because it's not the same level complexity either. Right. I don't have to have all of the answers possible in the whole wide world. I have a very smaller subset of things I need to consider. So I don't need all of that compute power. Right. I can do, I can have meaningful value add to this environment and it all be local and it all be on prem and it all be controlled by me and my data is not getting out anywhere. I'm not letting you out in, you know, third parties or Google or. And I don't have API calls to the Internet or backwards or anything like that. Right. That's, that's hugely powerful and that's what it's going to take in these OT spaces. Not to mention you start looking at, you know, DOD and government places and absolutely, you know, all of those types of things. Things. It's hugely valuable and obviously their air gap systems. Nuclear is another great example of that. Nuclear power plant has an air gap. Right. So that doesn't mean you couldn't do this, you just have to do it on prem.
42
00:37:30.000 --> 00:38:06.000
Of course. Yeah, absolutely. Again, it's always interesting to see again, as technology changes and allows us to mature how to respond in those environments and take into consideration an organization that needs to grow over time and Right. Achieve a level of comfort and a level of output and capability before they want to jump to the, you know, the next level. Right. So we're excited. I think we bring something meaningful and differentiated there. I'm looking forward to seeing, you know, how the market responds to it. But I think it's interesting, right, to talk through, you know, what's out there and how we're approaching that.
43
00:38:06.000 --> 00:38:36.000
Let me get to where I'm trying to get to two main types. There's obviously multiples, but two main types of customers that look to advance their cyberspace, especially in ot. Ones that have had something bad happen or ones that have a forward thinking leader that is trying, maybe they had something bad happen something someplace else and they're bringing those lessons learned in. How many are forward thinking organizations are looking for this type of thing in a mature way versus oh, we just got attacked and we need to do something or there's a regulatory requirement.
44
00:38:36.000 --> 00:41:12.000
Forcing me to do that would be the third reason, right? That would be the third reason would be a forcing function from a compliance perspective. You know, it's interesting. Different verticals, I think have a different technology adoption curve even within that vertical. Right. So you have an OT technology adoption curve and then within manufacturing you have a technology adoption curve even within manufacturing. In my experience, the manufacturing tends to be the most receptive to kind of more forward leaning innovative technologies. And again, even within manufacturing there are still organizations that want the bleeding edge and there are organizations that are the light majority laggard that want to see it demonstrated. I'd say that's the only industry or vertical that I would say as a whole is, I could say generically is more innovative in their approach or allows companies to be innovative in their environments. That's not to say there are not early adopters inside of those other verticals because there are, there may just not be as many. And that's really what we're, you know, that's why we're, you know, going to market. That's why we're, you know, trying to get our word out so that those companies that do want to be proactive and have the flexibility to do so know about us and those companies that need time to see the technology adopted and any kinks worked out, you know, and need to hear that, that reference, that referenceable, you know, that the guy that had an attack that you're talking about right now, we need to do something about it. They'll come in time, right? I like to say the, the market and our adversaries unfortunately do more marketing than
I ever could from a, you know, from a company perspective, when you do have a neighbor. Right. A neighbor facility. Right. A neighbor company that had an incident, you take that seriously. And I think it, you know, it used to be that you could almost be the, the ostrich a little bit. Right. You could almost kind of keep your head down and say, well, it didn't happen to me, it's not going to happen to us. And I think. Right. And I would say just judge by the willingness of people to engage, not as, you know, not our company, but just an OT cyber as a whole. I think that mentality has shifted to say, okay, like, it's not a matter of if, it's a matter of when, if we, we don't do something about it. Right. And so that's my perspective. I'm curious what yours is.
45
00:41:12.000 --> 00:41:57.000
Yeah, mine is the same. It luckily shifted over the years to, you know, I've been running this for 40 years. We've never had that problem happen. Blah, blah, blah, blah to. It's happened enough. I think everybody realizes it's not a matter of if, it's a matter of when. If I don't make significant changes and investments into my OT spaces, bad things can happen. And unfortunately, bad things in OT spaces, happening can mean lives lost. And that's obviously the impact and the risk is. Is higher because of those things. And the direct correlation, whether it be, you know, power outages and, you know, people lose their lives because they don't have electricity at home or, you know, something explodes and, and, you know, employees are hurt. Right. Any number of things, manufacturing, you know, all sorts of problems happen.
46
00:41:57.000 --> 00:42:58.000
Right. I was gonna say, I appreciate one of the really, I think bright points in our nation currently is there's a recognition of this at the national level. Right. From the policy level that critical infrastructure is critical for a reason and we have to take that seriously. Right. Not just from a compliance perspective, obviously that's still a driving factor. But from a funding perspective, organizations that want to do the right thing, that are trying to allocate resources towards solving a proactive. I'm excited to see that there's a recognition and opportunities for companies that want to not wait for something bad to happen to take advantage of those resources. Right. And those perspectives, because I think it gives investors confidence. Right. Company investors, stockholders, investment individuals that invest in companies like Hyperport, et cetera, all. There's a level of confidence there that I think is giving us wind in our sails as an industry to handle these things proactively.
47
00:42:58.000 --> 00:43:37.000
Well used to I would. My wrap up question was in the next five to 10 years. But I've stopped that from being such a long lead time because things are happening so fast and AI is changing and technology is growing so fast. So I've kind of adjusted that to say just, just say it a little bit differently, remove the time thing. But you know, all the things that are coming up, we know things are changing. It's an exciting space to be in. But what are some of the things, you know, maybe one positive and one thing that's scary. What's one thing that, that you see that you're excited about coming up over the hor this space and maybe something that's a little concerning in the same space and it doesn't have to be 10 years out because I know that's a long lead time.
48
00:43:37.000 --> 00:44:28.000
Yeah. I think what's exciting in the space is a little bit more higher level. Right. But the proliferation and advancement of data centers, right. The re. Nationalization of our critical infrastructure and onshoring things that have historically been offshored. Looking at charts, right, Data centers are obviously on a really high trajectory associated with the. But manufacturing and petrochem. There are investments being made across all of those verticals to bring back our core infrastructure to something that we can put our arms around as a nation. I'm really excited about that. I think that bodes well for us as a country, also for us as technology providers and practitioners. So that's the one thing I would say I'm really, really excited and I hope we see that continue right. Over the next three to five or ten years.
49
00:44:28.000 --> 00:47:55.000
Yeah, yeah, it's awesome. I agree. It's. It's one of those things that, you know, yes, it's cheaper to do things elsewhere sometimes, but I think we saw, it's another thing we saw during COVID is our supply chain was weak because we were pushing too many things off offshore. Which is fine and in good times. But when we need it, obviously if, you know, if China's making things and they need the same things that we do, it's not because they hate us thing, it's because, well, I'm going to take care of my people before I send things to you. Anything I have left over I'll send to you. But I'm not sending things and not sending it to my own people first. Right. So I would not expect them to do anything else, like anyone for that matter. So, you know, I love the fact that we're, we realize those things and it didn't, it wasn't too painful and hopefully we pick up on those things going forward. So no, I love it, man. You know, remote access has always been a big piece to me, you know, segmentation, you know, understanding my environment. But when I do all of those things, I've seen it from the beginning because we don't have enough skilled people. You know, all of these OT spaces many times are in the middle of nowhere. So hiring the right people for these spaces and I never have enough budget, so I don't have enough people. And they're also doing operational things and I'm expecting them do all these other things. So I need to have the ability to, to have a, a strong workforce that can provide that level of access and help into these spaces. But how do I do that in a secure way and help them without,
without making it more of a risk than it is a value? And it, in the past, again, my team would just drive, but even that made it really difficult because it took me longer because I'd have to drive out to the space and maybe it was a three month project and you know, it made it harder to do. When I have a way that I feel confident in and I can do these things remotely and I'm not adding too much risk to the environment, then that, that opens the, the possibility of how I can support, support how many people I need on my team, how many sites they can support, what types of projects we can do and all that kind of stuff. It really opens the portfolio of ability for me to support things, for me to be able to, you know, a regional team that's providing access so I don't have to have a high level skilled OT person. Because the problem that we've seen is we hire an OT person at a site, we train them up, we can only pay them so much because the market in that area only pays X amount of dollars. But then that same person, if they move to a big metropolitan city, can sometimes double or even more their, their salary. So you're going to lose them once they have the experience, more than likely they're going to move away because you just can't compete with them on that space. So having that ability to not lose them and say, hey, let's move you to corporate, you'll provide this access at a different level. We can pay you differently, but you're still providing that, that access and understanding that helps us with staffing, resourcing. Because we all know it's not just technology, it's going to solve this problem. It's people, process and technology. Right. So all of those things together, which is why I think Yalls product is. And products in this space are so exciting because they really help in all three of those. It help. It is a technology. Of course, it also enables other technologies, but it also enables the people and the process side of things, enhancing my ot, my lowering my risk, enhancing my cyber security, my posture, all that type of stuff. So that's. It's an exciting space to be in. I think that's why you see be a lot of conversations around it. And again, since COVID obviously everybody's been kind of forced down that whole that walkway of we're going to have remote access. How are we going to do it? Is a different question.
50
00:47:55.000 --> 00:48:19.000
Yeah, well, you have articulated the problem statement. Right? The challenge that we here at Hyperport exist to try to solve. So I really enjoyed the conversation. It's always great to talk with you. I think we've kind of gone in a number of different areas. I hope this is valuable to your listeners. I certainly enjoyed it. Hope we can do it again sometime soon.
51
00:48:19.000 --> 00:48:26.000
Absolutely. Steve, tell everybody how to get a hold of you where they could find out more about Hyperport, do a demo, all the things.
52
00:48:26.000 --> 00:48:39.000
Yeah, so I'm on LinkedIn. Just look me up. Steve Rutherford, you can reach out to us and connect on our website. Hypereport, IO demos, connection requests, all those things handle on the website. Learn more about us. I hope we can talk to you.
53
00:48:39.000 --> 00:49:01.000
Awesome. Yeah, definitely reach out to Hyperport. They're a great partner and a really cool technology and it's a really big need in the OT space. So definitely reach out to Steve. Tell them Aaron, Aaron sent you. Tell him you heard him on the podcast. All. All the things for sure. Awesome. Well, I will talk to you again soon, sir. Thank you for your time today. I appreciate the conversation and thank you for dealing with the technical difficulties that we had there. So I appreciate you, brother.
54
00:49:01.000 --> 00:49:06.000
Absolutely. Pleasure's all mine, Aaron. We'll talk soon. All right.
55
00:49:06.000 --> 00:49:30.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.