文字稿 🔗
Jackie Slaght: Yeah? Welcome to Beyond Tech, where innovation meets insight. I'm your host, Jackie Slatt. Today's episode tackles a critical but often misunderstood question. Is your facility actually secure or are you just assuming it is? In OT environments, most cyber incidents don't begin with sophisticated attacks. They start with exposure, unknown assets, flat networks, or misconfigured access points. And too often, organizations rely on outdated assessments incomplete visibility, creating a false sense of security. To dig into this, I'm joined by a special guest co-host, Wayne Hensley, a business development manager at e here at eTech Group. ⁓ Brings valuable client side perspective. seen firsthand the impact of cyber incidents from rising insurance costs to entire facilities being locked out due to undetected vulnerabilities. We're joined by our subject matter experts, Brian Gifford, an ITOT cybersecurity engineering lead at eTech Group. Brian works the intersection of automation, data systems, and cybersecurity, helping organizations design, secure, and scale connected environments across both IT and OT. So today we'll these ri where these risks are coming from. from what organizations may be missing and most importantly practical steps you can take to become more secure and proactive in your cybersecurity strategy. So with that, let's dig in and get the conversation started.
Wayne Hansley: Hey, thanks, Jackie. Hey, Brian, good to see you again, buddy. and I'm glad to be here. ⁓ we've been in c several client engagements and seen a lot of different catalysts for driving these things, but still ⁓ I guess OT cybersecurity incidents are still the the primary ⁓ for really digging into these things, ⁓ and not really planning and forethought. Can you can you expand on that a little bit for me?
Brian Gifford: It's all right. Sure, I ⁓ so it's it's easy not to fix the risk you don't recognize and until someone actually exploits that risk, we don't always wanna take care of it. and the industrial environment, the uptime and and operational output is what makes money. And fixing risks is not an immediate revenue generator, so it's not something that usually shows up on people's horizon. ⁓ so I I think that's it's it's easy to kind of get into your your day to day life and not think about the things that might happen, you focus on the things that are happening, ⁓ and And those risks and understanding those risks it only comes with experience and sometimes that experience can be pretty painful.
Wayne Hansley: Agree.
Jackie Slaght: So what do you think Brian or what have you seen when you're out talking with clients or hearing their stories? What what's the biggest risk for ⁓ for OT cybersecurity?
Brian Gifford: So the biggest risk that we've seen is segmentation. ⁓ you know, we we talk a lot about the the risks that are inherent in in OT because a lot of the stuff has a meantime between failure that's measured in decades. So a lot of it was built before security was really a thought. And a lot of the newer stuff, even even the stuff that's being built now, the security still really isn't built in as a as a starting point. It's built in as an add on or a ⁓ you know, something that we're we're tacking on after the fact. ⁓ so the the the stuff that most people talk about when we look at cyber risk We're we're looking at that outside edge. You know, we're looking at what can people see from outside of your network and what can people who are working inside your network do by accident. Usually it's it's not usually malicious, but it happens maliciously. But you know, what things can impact your operational uptime? and and that outside edge is the starting point.
Wayne Hansley: And Brian, ⁓ you and I have seen number number of different scenarios we've seen technology change both on the security side and on the tools for assessing risk, really doing the analysis. not in the past year, the past months, ⁓ it's changed pretty rapidly. position for me ⁓ old ways looking at risk and how we're approaching it now.
Brian Gifford: I mean AI is one of the biggest pieces that's changed, but the old way of looking at risk was I have a checklist, I need to run through my checklist in order to to be risk-free. And if I've checked all the boxes, then I'm good. It's not really looking at whether or not those boxes make sense for your environment. It's it's not if you're aligning to a framework, that's great, but if you're not looking at what the practical application of that stuff is inside your environment, making sure that it actually mediates a risk, then it's it it's not really useful. So the old way was you know, looking at ⁓ a checklist and going through an inspection check sheet. The new way is actually doing evaluations in real time. taking a look at penetration tests, taking a look at ⁓ a live look at your protocols and ports that are open inside a network, taking a a live look at how much traffic can actually pass through a link instead of what we assume the maximum output is, taking a look at hard segmentation, you know, can I actually pass traffic between two points that are supposed to be segmented from each other? I may have checked that box off on the list, but it might not actually be really segmented. So making sure that I've got ground truth, making sure that I have a really clear understanding of what actually is happening inside my network instead of simply checking boxes off, that's probably the the difference between then and now.
Wayne Hansley: And one of the things that you and I have seen working with several different clients is you know an assessment a lot of visibility on here's the state of things right now ⁓ a a kind of a plan ⁓ priority of hey here's what we can ⁓ what we can do to to mitigate some of those risks. what about continuing visibility? Because several clients are now leveraging ongoing tools, just a snapshot, but let's look at what's changing two months after the
Load full transcript
assessment.
Brian Gifford: Sure. I mean our our operational environments are not static. the plants are constantly changing, they're constantly evolving. There's new technologies or just replacement parts. ⁓ if a a switch fails, I the the engineers that are putting that network back together may not put it back together the same way. Or if a new part comes in it might have a different firmware version or it might lead to other changes that have to happen down downstream from that in order to be functional. ⁓ and those changes that naturally happen in an operational environment over time They're not always captured. They're they're very rarely captured. So having real time monitoring, having something that's keeping an eyeball on your your environment, ⁓ not so that it's every couple of years, but every couple of minutes, you're you're gonna look at ground truth and be able to see exactly what the status of that environment is right now, which is huge because it means again, if I'm if I'm checking boxes on a on a checklist, that's one thing. If I actually know exactly where my risks are at this moment, you know, minutes after an engineer has finished installing a box that says that it's good. And I can go and check those against vulnerabilities or what ports are open to it, how it's segmented from the rest of the network, what else it might be broadcasting. All of those are things that will help me understand my network immediately instead of waiting for downtime to happen. I can get ahead of it and stop the downtime from happening at all.
Wayne Hansley: And just to add on to that, one of the things that done with these clients is we both monitor this ongoing view, this ⁓ this portal into what's happening ⁓ ⁓ has been valuable in that sometimes we know before ⁓ client knows and events happen.
Jackie Slaght: That's a that's impressive. I know and from past conversations my kind of limited understanding of ⁓ and w and how attacks happen, ⁓ sometimes ⁓ you may have a have someone access the network and just kind of sit there for like months just kind observing. So if you can stop that before do anything, that that feels ⁓ feels like a huge step in the right direction. ⁓
Brian Gifford: Yep. And that's we talked a little about AI. AI is starting to be leveraged on some of that stuff too. We're seeing those in in network sims that are allowing us to see so if someone's sitting inside your network and they're they're watching things, they have a command and control link, they've got beaconing that's happening. Those things are ⁓ a a message style, there's a there's a cadence to those that can be identified by artificial intelligence because it's looking for patterns. And if we see something that's pinging an outside address, some some faraway IP someplace and it's doing so every couple of minutes or every couple of days. That's something that the AI security tools are are trained to to identify that that's not a typical thing. That that's something that
probably indicates a a bad act or at least something we should pay attention to. So a hundred percent if someone does compromise a system inside an OT environment, being able to see that in real time, having tools that are able to recognize those patterns that happen over time, those are those are really important pieces.
Jackie Slaght: So I think I I think you've kind of touched on this a bit and we've kind of already talked about it, but What does network visibility actually mean in the OT environment? Is it kind of just how things are connected or or what is it showing?
Brian Gifford: So network visibility can mean a couple of things. We want to understand our logical topology. So how how a network is laid out in physical space versus how it's laid out in logical space. So I might have everything connected to a switch, but the devices that I have on there may need to operate as if they're in a ring. So the the physical and the what's happening under the hood might be a little different. ⁓ so part of that is visibility of topology. And if say one of the pieces of that logical ring breaks, if I have network visibility then I know that and I can respond to that immediately. I can also see things like if ⁓ if a a device fails and starts broadcasting help traffic, hey, you know, come find me, I've got a problem. ⁓ that can impact other devices. So the fact that it's broadcasting screens for help can actually impact older PLCs, can cause other problems in the network, and if we identify that through our network visibility tools, we can go and fix that device before it causes other problems and and creates some of that operational downtime. We can also see other pain points, we can see misconfigurations, the Network visibility really means that you understand what's happening in your network in in real time. It's ⁓ some of those real time management tools we've been talking about. ⁓ it also gives you the ability to understand what needs to change over time. So expenses that happen when we don't expect them are bad news. you know, if we have an expense that comes up and and the C suite gets a bill, that that's not a good thing if we haven't talked about that stuff ahead of time. But if you know something's failing or if you know the lifetime of something, then you have a planned expense. And the planned expense is something that's much more palatable. We can figure out how we're gonna deal with it. We can approach it with a phased plan for for accomplishing remediation. so having planned changes is always a good idea. And network visibility tools give us some of those as well.
Wayne Hansley: to be edited out. I'm going to couple of questions here for for Brian. ⁓ Brian, we talk about the assessment and kind of ongoing monitoring tools and stuff. So I'm going to take a step back in that like most all solutions e Tag provides our clients, ⁓ it's custom, it's tailored to what their needs are. ⁓ so it's customized. So ⁓ outline me we're we're talking about a f a first time assessment.
Jackie Slaght: All right.
Wayne Hansley: what are what's the what's the strategy and tactics we're using that are available to us and as a follow of that already acknowledged that we need to monitor and it's always a moving target, so how often should be repeating this? ⁓
Brian Gifford: Yeah, so that's a great question. ⁓ so we we have a number of different products and it really depends on what the customer's pain points are. So the strategy always starts with an interview with the customer. We need to find out what their requirements are. And part of that's gonna be what the customer believes their requirements are, and from our experience we're gonna we might see a a slightly different path. If they're looking at network performance but we're identifying that they have a lot of really old stuff in their network, then it may not be the the IT O T network assessment we want to do. We may want to do our inventory assessment instead. ⁓ because it's and and we'll talk through what the differences are between those two assessments of the customer. If they want to do both, that's an option as well. So we have four essential products that we go through for assessments. we've got the ITOT network assessment, which if you're looking at Purdue model layers, it's Purdue model layers two, three, and four, and that's all your network infrastructure. So it's your core switching, it's it's the the core control systems, down to your distribution layer switching and down to your access panel switch. So it's all of your network stuff. How am I transmitting information back and forth around the the plant or the operation? ⁓ and then the next piece is is an inventory assessment where we look at the devices themselves. So we look at anything with an IP address or MAC address, you know, PLCs, HMIs, drives, stuff like that. And we get a very clear understanding. We get a complete inventory of those devices. We look at them all the way down to the catalog number, we find out what their firmware version is. We give you an understanding of life cycle on all of those pieces. ⁓ and that has been a really useful tool for for ⁓ companies to be able to understand what their current risk is from a lifecycle standpoint. How old is this stuff in their inventory? you know, what needs to be replaced, what's what's been operating for twenty years and might gain a little bit of love. ⁓ it's a it's a great place to start a lot of companies. there's a lot of companies that that find that product really valuable. And a com combination of the two is is always available too. ⁓ at the top of that layer, we do cyber security risk assessments and cyber compliance. So we take a look at a company's
Jackie Slaght: Mm-hmm.
Wayne Hansley: I know.
Brian Gifford: Cybersecurity posture, one of the things that's happened in recent years is insurance companies have tied your cyber risk to your premiums. So if you're not compliant with a cyber risk framework, you
have more expensive premiums. So tying dollars to that risk compliance has given companies an appetite to start approaching these things instead of waiting for something to happen. They're actually looking to be proactive, which is what the insurance companies are looking for. So doing a cyber risk assessment and doing a cyber compliance assessment, that gives us the ability to help with company understand what their current posture is? You know, do they have programs and policies that are in place to support cyber compliance? Do they have business continuity plans or incident response plans? do they have a password policy that makes sense? they have a a mobile device policy that makes sense. And we help them get to the point where they understand what their risk is. And it's a product that they can hand to their insurance company to help reduce some of those premiums. And then As a kind of an added piece, we look at a Wi-Fi assessment, which will give a company a clear understanding of all of the radio frequency stuff that's happening inside their environment. So Wi-Fi interactions across all three bands, exactly how many access points I can hit from any given point, if I have overlap, if I've got frequencies that are competing with each other, ⁓ it's a a solid understanding for ⁓ a ⁓ a growing market. A lot of companies are starting to move to wireless because it's easy to deploy to understand where those pain points might be. well that might cause downtime or interference or performance issues inside the operational environment. So there's a a wide catalog of stuff that we can accomplish in terms of assessing your current status for a company and and it it's not a one size fits all. ⁓ I mean these are concrete deliverables, but it really depends on what the customer's pain points are. We usually start there.
Wayne Hansley: Good, thank you. ⁓ and just to kinda as a follow-up, this is an observation, you and I have been involved in a number of asset assessments, and you've you kind of framed that into reducing su mature security risk, meaning that and insurance you know, cost reduction justification stuff. ⁓ of the things that we've seen, we deal a lot with clients in regulated industries, food and beverage, life sciences, chemical, consumer goods. And it's that their assets be up to date for them to make product for them to sell. it's a it's not just a security risk or staying up and going, it's ⁓ I'm gonna sell my if I'm gonna sell my product X, then I need to be up to date in in all these areas and be able to document that and show it. And so it's that's yeah. So yeah, keep my plan up and running so I can sell product is ⁓ is pretty key. ⁓ most of them.
Brian Gifford: Yeah. Validated process, yeah.
Jackie Slaght: Ha ha ha.
Brian Gifford: Roger.
Jackie Slaght: how often ⁓ should an organization be re looking to ⁓ like to reassess the environment and why is that so important? ⁓
Brian Gifford: it it depends on the the pace of the company. We kinda talked about those leave behind products that are gonna give you visibility full time. Those are the ideal. If I have something in my environment that's giving me an up to date map, ⁓ me ground truth day to day, that's the the best answer because it gives me something that I can I can point to at any given time and I can see the change over time as well. ⁓ so if a company's not going to do a service like that then It really depends on how fast the company changes. If they've had the same stuff and they're not making changes, if they don't have old equipment, if it was a greenfield project from five years ago, then maybe they don't need to do it quite as often. Maybe once a year or once every two years might be something that will will still give them what they need. ⁓ but I would still highly, highly recommend looking at tools that will stay in your environment that will give you the ability to understand what's happening in real time. ⁓ I emphasizing that ability. I mean it's it's visibility, it's analytics, it's cost, it it's uptime. I I I think it impacts every aspect of the company's business operations.
Jackie Slaght: Yeah, well and I think to your point, like the every things are continuously changing. So something that is continuously monitoring and and keeping you up to date is is very
Wayne Hansley: Let's roll back to results for s just a second, Brian. Yeah, we're looking at an an assessment going in whether it's assets or exposure or yeah, bandwidth, all those things. What are the most common things that your team is seeing? What's the top five?
Jackie Slaght: Yeah.
Brian Gifford: top five issues. It's the the number one I would I would I would say okay. Exposure risk is a little different. So the the I I would say that the top issue that we see is segmentation. So the exposure of assets inside an OT environment to the internet. a that's a huge one. So I digress just a little bit, the kind of the the way an attack happens. ⁓ An attacker they they always start with the first phase. The first phase is reconnaissance. They always want to go find their target.
Wayne Hansley: Yeah. Exposure exposure risk. Let me let me be specific.
Brian Gifford: And they may not be looking for whatever the company is specifically. They're looking for a company with exposure. They're looking for a company that that has something that's open to the internet, that can be accessed, that is running a protocol that that's known to be compromised, or that has a piece of ⁓ piece of equipment that they know they can get into. So the companies that are exposing their stuff to the internet are are making themselves those targets. They're they're opening themselves up to that initial search, that initial reconnaissance. And there are sites that all they do is crawl the internet all day looking for and mapping what open ports and what open IPs you have on your network. So finding that stuff without exposing that if a bad actor wants to find those things, they
don't have to necessarily show you that they're looking at you at all. They just go browse one of these sites that looks at all this stuff full time. They find something that meets their target criteria, and then they go attack that target. So the first most important thing of in in top five, I would say the top three are exposure. The the top three are that outside edge of your network where You're putting yourself in one of those lists where it's easy for them to find you and target you because you fit the bill for whatever their target profile is. ⁓ next one is probably age. ⁓ a lot of times because of the way OT works, because of talked before about the meantime ⁓ measured in many years, ⁓ it's easy to operate with older equipment. And and that doesn't mean it's a bad thing, and it doesn't mean that those equipment shouldn't stay in the environment, but we do need to understand what risks they offer. They may not have any security, they may not have any visibility, they may not be able to. participate in new analytical tools, which means you may not understand what they're doing at a given time. So understanding what those risks are from an age standpoint, I would say is probably number two. And then for number three, I would look at secure remote access. A lot of times vendors and companies need to be able to access their equipment to do maintenance on them, and they don't want to necessarily have to pay someone to come out to the site to do that. it's easy to take a shortcut and offer someone access from the outside of your company to come in and and manage one of your pieces of equipment. And That might be safe for one time. maybe. ⁓ wouldn't recommend it, but it's it's kind of safe for a short duration of time. But it's very easy to forget that you've left that port open or you forget that you have that thing still connected to an outside port. So when we do those things, it's it's easy for that to creep up on us and end up with a bunch of things that are exposed to the internet by accident because we haven't shut those things off after the fact. So having a good secure remote access program, making sure you're tracking all that stuff when you open them, make sure to close them.
Jackie Slaght: Yeah.
Brian Gifford: preferably having a tool that does so securely on its own and making sure that it only has ⁓ access to the things you want it to for a short period of time. I I think that's number three.
Jackie Slaght: so ⁓ those are the top risk that you see. What are some quick wins that a client could take to reduce these risks? always the most thing is keeping running without you know, taking too much downtime to implement any of these solutions.
Brian Gifford: or or costing crazy money on the way in because a lot of times your your capital expenditures it's very tightly controlled. It's difficult to carve that money out. So understanding and having planned controlled costs, that's that's really important in these projects. So I I would say
having an understanding of ground truth to start with, to know what your pain points are, that's that's the starting point. We really need to start with understanding what the scope of the issues are and and from there we can prioritize.
Jackie Slaght: Yes.
Brian Gifford: And once we have a prioritized list of what the customer needs to do in order to be safe, in order to stay uptime, in order to provide visibility, then we identify what a phase remediation plan looks like so that they don't have to carve out all of it at one time. We can give them some of the remediation, the most important stuff up front. ⁓ so does that answer the question or did I miss a piece of it?
Jackie Slaght: Well so I guess what ⁓ what would you start with? So once you have this phased approach, what would the like first first that could help reduce the risk right away?
Brian Gifford: So say say a customer has a a a network that's very challenged. They're open to the internet, they don't have any segmentation, their IT and OT networks are operating in the same area, maybe using the same domain, so everything is really connected to everything else and they have internet access. they have devices that are daisy chained, so we have instead of ⁓ using say star topologies that are very redundant, resilient. They have ⁓ a switch that's attached to a switch that's attached to another switch all the way down the line. And if any of those switches fail, you lose everything down the line from that point. ⁓ if I have a network that has all of those problems in there, I'm probably going to start by looking at the age of the devices and seeing what their operational requirements are. For me, the first thing is going to be the outside edge. I want to make sure that they're secure from threats outside. But I'm also focused on security. That's my primary, that's my my passion, it's where I come from. So they might be more focused on
Jackie Slaght: Yeah.
Brian Gifford: the operational uptime, in which case the first thing we might want to remediate is to look at some of those daisy chain switches. We might want to to alter how the plant is laid out in terms of the the network topology to make sure that they've got redundant links so that if any piece of that fails, they still have uptime and they still have the ability to identify it and go and fix it. And then ⁓ after I have the the network segmentation and the back backbone kind of completed, then I'll look at secure remote access, ⁓ making sure that we have very tightly controlled ⁓ firewall rules, I mean it's it's more the the security focus at that time. ⁓ most plants are focused more on the uptime piece than than the security piece until we get the insurance money involved ⁓ on it. Or unless they've been hit already. And that's a that's another thing that we've we've seen a lot. We'll we'll see companies that have been hit that are now they really wanna ⁓ engage on this because they have the momentum. ⁓ so the security stuff becomes more important in the operational ⁓ uptime. And they don't have to be exclusive.
Jackie Slaght: Yeah.
Wayne Hansley: Yeah.
Brian Gifford: establishing a better network topology inside your network is gonna give you both.
Wayne Hansley: Jackie, I'm going to take a unplanned side trip here. ⁓ based on comment. You you talk about how ⁓ OT IT sometimes get blended together and we've also seen where they ⁓ need operate, need to be monitored, they need to be managed ⁓ drastically different. Can you on that? Because we I we we we live eTech lives pr primarily in OT environment.
Jackie Slaght: ⁓ I'm excited.
Brian Gifford: Plan trip to the best.
Wayne Hansley: Which is very different than IT's view of the operational world so in many cases.
Brian Gifford: Yeah, totally different priorities, right? So your your OT's priority is uptime. You know, can I stay up? Can I stay productive? Can I stay efficient? ⁓ IT's priority is more on the security side, they're more compliance based. there's there's more more of an ability to take the time to to kind of enact those rules and policies. Sometimes the rules don't make sense, but we still have the time to enact them. so
Wayne Hansley: Okay.
Brian Gifford: it it's it's a difference in kind of practical application versus you know having a little more flexibility in the IT space if something goes down we get sad because we can't get access to our our smart sheets. ⁓ but we're not losing money in the in the plant, right? So there's definitely if if I'm managing both networks by the same set of priorities, especially if IT is primary because IT usually has more of the network experience side. So a lot of times you see that as the the way it happens is IT is managing OT and they're managing it using IT kind of priorities.
Wayne Hansley: Mm-hmm.
Brian Gifford: you're definitely gonna see some conflict. And we often see OT engineers and the IT space conflicting over what should happen and why because of those differences ⁓ requirements. ⁓ and managing those relationships, trying to help them kind of bridge those gaps and and achieve synergy without necessarily giving up each other's silos is is one of the things we're pretty good at too.
Wayne Hansley: Thanks.
Jackie Slaght: Can can you share an example I when we have gone in and completed an assessment ⁓ and a of risk that the client was not aware of?
Brian Gifford: ⁓ sure. So we we went into a plant ⁓ a couple of months ago and we did an assessment and we identified we talked about daisy chained switches. They were not aware that they had two of their lines that were entirely daisy chained. ⁓ so meaning ⁓ instead going from from say a centrally a central switch or a central switch stack where if one of my switches fails, I still have the other one to fall back on and I have redundant links that are outbound, so kind of like a spider.
Jackie Slaght: What does that mean? Sorry.
Brian Gifford: ⁓ instead of that I'd have say a switch at one end of the line that
then connects to another switch part of the way down the line that then connects to another switch and then another switch. Ideally I would have one distribution switch or a distribution stack, a redundant stack that would connect to each of the switches on the line. So I have the ability to fail in any one of those points and I only lose a small portion of my line. But if I have switches connected to switches all the way down the line, if I lose an upstream switch, I lose all of the switches down below that point. ⁓ so it it increases the risk of failure what what my we call the blast radius. It increases the blast radius of a of failure at some point in that network.
Jackie Slaght: It's reminding me of the old Christmas lights where if one light went out, they all went out. Okay, sorry, that was just wanted to make sure I I was understood.
Brian Gifford: Yeah. Yeah. One of my favorite songs. Yeah, sorry. No, but it wasn't expected that yeah, the customer didn't know that they had that going on in their network, so we identified that and that became a a very high priority because we saw the risk in there.
Wayne Hansley: So what I mean, let's go back to my the top three. are the top three gotchas? ⁓ I didn't know I had that list on assessments and when we go into a c a a plant and start uncovering stuff.
Brian Gifford: so secure remote access is a big one. A lot of times we'll see companies that will start down the secure remote access pathway and they'll start with Ewans, which are are great tools. They do great things, but they're kind of specific to one location. They don't do a kind of a centrally managed option for for the the standard E wons that we see. and we'll find out that they've got stuff that's ⁓ you know connected to a bunch of different things that are still exposed to the outside, you know, kind of that leaving leaving those exposed ports that that can be scanned and people will notice them ⁓ because they're they're an easy ingress point. another is we we talked about some of that topology stuff. So those gotchas identifying that there are ⁓ that have connected switches just where they need switches instead of necessarily in an order that makes sense. They're not looking at that star topology and and making themselves a redundant link so that they can absorb a failure or if something goes wrong, or if someone kicks a plug someplace ⁓ and and they lose part of their switching, they still have access to their network and they can still continue to operate. and then I would say vulnerability patching. So ⁓ a lot of times for our ⁓ HMIs and our engineering workstations, they're running Windows or sometimes Linux. And because they're they're not connected to the network, if it's done correctly, then they're not connected ⁓ outbound into the internet, which means they can't pull updates, which is great because they're segmented, but it's also not so great because it means they're very behind. So having a secure patching standard, so knowing that you have a patch in cadence and and ⁓ making patches happen. when you have downtime in the plant, that's probably another really big one.
Jackie Slaght: So how when I guess after an organization has completed an assessment or we've worked with a ⁓ on a on an assessment, how do they how you recommend or how do they balance the priorities of like a cybersecurity versus visibility versus I guess any other ⁓ updates that they may wanna ⁓ wanna make given they've found out during the assessment?
Brian Gifford: That's why they use us, because we have the experience of people who identify some of those priorities. So it goes back to those conversations. We want to understand what their priorities are as a company. You know, not necessarily in terms of remediation, but understanding what makes the most pain. You know, is it is it downtime? Is it the the risk remediation stuff so that we we can start to save some money on those cyber premiums, the the insurance premiums. ⁓ we start off by conversations with the customer to really understand what they need, ⁓ and then we'll give them recommendations on what we think the
Jackie Slaght: Yep.
Wayne Hansley: Yeah.
Brian Gifford: priority should be. And we'll back those recommendations up with hard data. You know, this is the impact of these things. If you don't update these PLCs, you've got a 30% risk of losing one or two of these in the next two years. And the cost of your downtime because you don't have spares on hand are going to be approximately whatever it is. It depends on what we're doing. If if the engagement includes a budgetary estimate on on downtime, because we do risk management there too. So it it it really it's a a two way conversation. It's not just us identifying that stuff and handing it to the customer. It really needs to be a conversation with the customer to make sure that that we really understand what they need, that we're we're giving them recommendations that make sense for their situation and for their budget and for their requirements.
Wayne Hansley: I so Brian, we've talked about segmenting IT and OT with different priorities and stuff, ⁓ but a lot of the applications and data that we're helping clients manage and put in place are are bending those lines. They're punching holes in those lines. So we're we're pushing data down, we're collecting data in historians and data lakes are pushing data back up. How do you balance all this as these lines blur, how do you manage continue with different sets of parties, how do you manage that ⁓ visibility and security and and ongoing assessment?
Brian Gifford: Well, we have to figure out risk tolerance for the customer and what they want to accomplish. So one of the biggest things that we're seeing is the AI and cloud. ⁓ so using AI generates data that's fantastic. We can see patterns very quickly, we can we can get information out of it that's amazing, but that information isn't always accurate. So understanding the limitations
there are important. And then cloud, a lot of the best tools live in the cloud. So it means that a a customer who might want to siloed network, something that is entirely separated from the internet. Now I've got to add tools that are opening them up to the internet in order to use some of the visibility or analytics that they require to work efficiently and effectively. balancing those requirements, like you were talking about some of the the risk inherent in that stuff, we we are seeing with more integration there is more risk. So being able to balance that stuff is a a function of separating, we talked about blast radius earlier, right? Separating stuff out so that if something does happen, I'm minimizing the amount of space it's gonna happen in. So if I have a a function in my OT floor, I'm gonna make sure that that function is separated to the extent possible from the other functions, with the exception of what needs to be sent between those two points. We call that least privilege. We're we're minimizing our output, you know, to to the only only the stuff that really needs to be transported. and the same thing at the outside edge. If I need to push stuff up to the cloud and and back down from the cloud, I'm gonna minimize the size of that. If I can put middleware in between that I trust so that can kind of look at that data that's going out and look at that data at the as it comes in to make sure that it's not being compromised. I'm going to use that as well as a a way to validate that I'm not bringing something into my environment that I shouldn't. So there are a lot of tools that we can help to enable that will still allow those advanced functions to be used like AI in the cloud. But we can use them safely within a validated environment just by making sure we understand what the customers' requirements are for validation.
Jackie Slaght: So looking ahead, where do you see strategies evolving for cybersecurity in the next I three to five years? Or I don't know if it should be a shorter period of time or a longer period. changing quickly.
Wayne Hansley: Yeah.
Brian Gifford: say can be answered in two letters, AI. so it's ⁓ ⁓ it's it like I just talked a minute ago about how AI is ⁓ we don't really trust it yet. You know, we've we've all used chat DPT and gotten some very strange answers back when we ask a question. so we're we're not entirely sure that we trust what AI is doing for us, but at the same time we also recognize that it's become a required tool, that we really can't operate at the velocity that we need to without it. We're seeing that in in the cyber security space as well.
Jackie Slaght: Much like everything else.
Wayne Hansley: Yeah.
Jackie Slaght: Yeah.
Brian Gifford: ⁓ that ⁓ if I have exactly the same stuff ⁓ and I feed it to my cybersecurity tool that's balanced by AI, I'm gonna get different stuff out both times. That's not a bad thing. It might see different insights the second time that I didn't see the first time. But the ability to look at patterns, to look at a large amount of raw data and get something out of it that makes sense and do so very quickly, it it's absolutely invaluable. But the bad guys are using it too. AI also makes it easy for me to take a look at a network if Instead of looking for open ports, I decide I want to attack ETEC itself. Right? And I'm I'm looking at ETEC's open ports on some of these tools that have scanned some of our stuff. AI is going to give me more of an opportunity to see what exploits there are available on that stuff because I can immediately ingest all the information that I have available and and take a look and and with a a the database that's available to the AI, figure out exactly what the best way to attack is. ⁓ it is terrifying. So without that support, we really need to have AI both defensively and and for the bad guys are using it offensively because it's it is an an amazing, amazing tool with an immense amount power. the evolution of security right now, we're we're seeing more tools that are more integrated. We're seeing more tools that are able to give us answers faster. We're seeing tools that are able to respond in real time and make changes to our network with or without us. And and that that is both good and bad. But AI is definitely the place that we're starting to see that that we're we have been seeing the most change.
Jackie Slaght: Yeah, I have just one final question before I get to our fun closing questions, which I will ask Wayne and Brian because I want everyone to participate. But ⁓ my last question is what ⁓ like w if there's a client listening or anyone I guess they don't even have to be a client, but anyone listening, where should they start? ⁓
Wayne Hansley: Yeah.
Jackie Slaght: if they you know, cybersecurity is a priority and something they need to focus on. Where where do they begin this
Brian Gifford: I may have mentioned this once or twice, but I think it should start with a conversation. You know? I think, you know, those those conversations we have some very talented people, some people who are are very good at this stuff. And I think ⁓ having a conversation to understand w what you're looking for. I mean if if someone's coming to us, they have a need already. and that that defined need will help us starting point. It gives us a place to start the relationship and and start working toward what the customer needs. So ⁓ beginning a conversation to make sure that we're really clear on on what you need, will help us to understand how to achieve it. And we have an en some some fantastic people and some amazing tools. We we are very good at this. ⁓ so I I look forward to this conversation. No, it's it's not.
Jackie Slaght: Yeah. It's it's not a necessarily one size fits all. It's yeah. Do you have anything else that you want to ask before I move on to the the fun questions, Wayne? Anything that we missed?
Wayne Hansley: ⁓ I just just just one we've we've done a lot of differentiation here.
it Brian, you and I have both worked on Greenfield and Brownfield installations and kind differentiate. I mean it the the tactics and the strategy is different, but the end result, the end goal is this is the same. point out a couple of tactical differences in in the well ones what we've been exposed to. ⁓
Brian Gifford: Sure. It's Yeah. it's it's built in versus band-aid, right? If I if I start with a green field and I have a customer who has a an appetite to bake security and it makes it very easy for us to do that at the low level. We can start off with that assumption. It gives us the ability to choose equipment that supports what we need, ⁓ to to choose new OT gear that's actually gonna have security baked in. it it allows me to really build it in from the ground up, which makes it less expensive to implement, and it also means that every process
Jackie Slaght: That's a that's a great ad, Wayne.
Brian Gifford: And every piece of it has all that stuff already understood. If I'm working on a brownfield project, I am applying band-aids. You know, there's there's definitely a difference there. ⁓ we're we're dealing with an existing ⁓ we don't want to take the the the brownfield down for an extended period of time. You know, even if we're doing a a full renovation on something, you're still looking at pieces of infrastructure that are going to be there regardless. There's a lot of ⁓ investment that's already gone into it that we don't want to replace if we don't have to. So
Wayne Hansley: Disruption and
Brian Gifford: the the approach is very different. We're we're really looking at that blast radius. We're really looking at the segmentation as one of the primary pieces to make sure those older devices that don't necessarily have a lot of security built into them that they're they're really focused in a small area so that we can we can keep them from ⁓ you know from from pushing outward if something bad happens. ⁓ so it's it's definitely a different approach because we wanna in a brown field we're usually we're trying to achieve a goal but we're trying to do so on existing infrastructure and we're trying not to replace the the most expensive stuff if possible. You know, we're we're minimizing cost. so it's a a a function of how much ⁓ can replace, ⁓ you know, and and what do we need to mitigate instead of replace.
Jackie Slaght: Well that was that was a great ad. okay, so this ⁓ we're getting into the fun portion ⁓ the episode. ⁓ true, that's true. That was that was not agree. I did that's this what you talk about, that's what you like. So it is all fun and I enjoy learning about it. So but this this I thought was a good topic to to
Brian Gifford: I've been from this whole time. I don't know what you're
Wayne Hansley: In his zone right now, man.
Jackie Slaght: Transition us into these closing questions, but what is one myth that on cybersecurity that you wish could just make go away and never have to talk about again? ⁓
Brian Gifford: Sure. ⁓ cybersecurity doesn't have to be expensive. I think that's the first one. there's a lot of stuff we can do ⁓ you know, even with just a little bit of consultation that will help us to become more secure without having to spend a silly amount of money. I'm saying that cybersecurity can't be expensive. It absolutely can be. but some of the stuff we can do to change like the the the most cyber attacks start with fishing. so fishing education is not something that needs to be super expensive, but it's One of those things we can do that immediately lowers our risk at the outside edge. there's there's it it doesn't necessarily have to cost a a substantial capex in order to get you a little more secure.
Jackie Slaght: And one of a ⁓ I don't even remember who I was talking with. It might have been on a webinar we were producing a couple years ago, but they said one of the the biggest, ⁓ not maybe not biggest, but one way that people are but threat actors, hackers get in is by like the set password on devices that have never been changed. ⁓
Brian Gifford: Default passwords. Yeah. That's a huge one. ⁓ default passwords are the bane of securities' existence. It's bad news. ⁓ but I mean that's your your phishing attacks. Most hackers are not hacking into things anymore. You know, there are exploits, but the vast majority are just logging in. They're finding credentials on the web. So a lot of people don't like to remember a lot of passwords, so people reuse passwords all the time. So say your Google password was was hacked, your Google password is very likely to have something to do with the password user work. So if someone identifies a personnel that l that works at a company and they can find on the dark web and there's there's whole marketplaces for this stuff, if they can find your passwords for other stuff on the dark web, it's easy for them to figure out what your password is inside. It is the the opening edge. So after reconnaissance, the next thing is ⁓ on to to get credentialed access. and credentials access is not as challenging as it should be. And that's where that those phishing attacks come in and that's where making sure that you've got strong passwords and you're using strong passwords on a regular basis, that's where that stuff starts to become more important.
Wayne Hansley: cost effective way to mitigate risk yes.
Brian Gifford: Yep, low cost. Yep.
Jackie Slaght: Wayne, do you have a myth that you would like to go away or
Wayne Hansley: mine's not nearly as technical or ⁓ well thought out. as ⁓ the myth that hey, I've got a firewall, I'm okay. firewall is one little in the ⁓ And you know, think firewalls came out, I got my firewall set up, I'm I'm good. Then ⁓ like I said, Brian says, you go in and you find all these other open access points set.
Jackie Slaght: Ha ha ha.
Brian Gifford: Good one.
Jackie Slaght: Ha ha ha.
Wayne Hansley: Walk right around your firewall. There the firewall sits and it's beautiful and it's humming away and the
lights blink, but everybody else is talking around it. So yes.
Jackie Slaght: That's a good one too. ⁓ If you automate one thing in your life, what it be?
Brian Gifford: ⁓ if I could automate one thing I would think it was the drive to work. You know?
Jackie Slaght: You can get one of those self driving cars. Or I actually don't know if they're for sale yet, but I I know they exist.
Brian Gifford: It's they're getting there, but yeah, you know, you talk about trust. I trust trusting a machine to drive me safely without killing anyone or myself. I'm not there yet. Yeah, that's I would I think that's that's probably the first thing that I would automate, yeah.
Jackie Slaght: That yes. What about you, Wayne?
Wayne Hansley: ⁓ probably priority and schedule management. I mean, just we've we've got so much going on. ⁓ and and and like cybersecurity and risk, I've got so many channels that I have to monitor and prioritize and be able to find stuff, prioritize it and and get it on my schedule in the most effective, efficient way would be awesome.
Jackie Slaght: That was somebody else's too was like. Yeah. I think it was Sara's answer too, was like calendar management was the thing she wanted to automate and I was like, that is a good one.
Brian Gifford: Genic AI is coming that's gonna I mean we're we're starting to see people building out agents that will do that for them. Multi your your multi stream communications management, everything from signal to teams to your texting to email, all of it and and one shot, one painting glass. It's pretty cool stuff.
Wayne Hansley: What about you, Jackie?
Jackie Slaght: Yeah that ⁓ man I mine is usually kind of boring. I just want somebody to like do my laundry but include it in like putting it away like
Brian Gifford: Wow. I was gonna say you have a washing machine, that's a robot already. You're good.
Wayne Hansley: Yeah.
Jackie Slaght: I yes, it washes and dries, but does it ever make it back to the closet? No. ⁓ how would you describe your job to a five year old?
Wayne Hansley: Doesn't fold iron and and place back where it needs to be, right?
Brian Gifford: Ooh. sit in front of a computer and I look at the colors on the screen and I hit keys ⁓ change the screen so that the colors match what I like.
Jackie Slaght: Yeah.
Brian Gifford: That's that's what I do.
Wayne Hansley: I'm gonna I won't answer the question, but I'm gonna elevate it to middle school level. 'cause I had the opportunity past couple of years to go to a middle school here in Riley near our office, and meet with ⁓ the population, but then a couple of the robotics classes and just talk about automation and robotics in the world today. ⁓ And got to got to use some real live examples of, you ⁓ right robotic and
Jackie Slaght: Okay. ⁓ my gosh, I love that.
Wayne Hansley: it really trying to explain to them that robots aren't R2 D two and C three P O and you know, it's you know, they they're made for a purpose and they're if you is it d dangerous, boring, applications that you can turn over to something that'll do it ⁓ and over and over again. So yeah, that experience and being able to explain at a ⁓ middle level
Jackie Slaght: Ha ha.
Wayne Hansley: just to spark their interest in automation and engineering was pretty eye opening. It was pretty interesting.
Brian Gifford: That's awesome. I bet that was a lot of fun.
Wayne Hansley: It was.
Jackie Slaght: That that is awesome. I also I will just add and do a shameless plug for future Beyond Tech episode. We are currently prepping one about ⁓ careers in automation and how people have joined our team. and that idea was brought on because there is not like a system integration degree. ⁓ So coming into this field kind of from a lot of different Engels perspective experience and and it's great. So yeah, stay tuned. That one will be coming out soon. ⁓ and my last question is what would you like to see us cover on future episodes of Beyond Tech? Aside from the careers one that I just teased.
Wayne Hansley: Cool.
Brian Gifford: I think Wayne's robots, I ⁓ seeing robotics would be fantastic. You know, I'm I'm kinda stuck in the IT space most of the time. I'd love to see some of the ⁓ you know, the cool O T stuff.
Wayne Hansley: Yeah, that would be good. And yeah, one of the one of the things I'll absolutely one of the reasons I move from engineer to business development and I call myself a client success advocate is I get to walk into a lot of different plants, making a lot of different things and a lot of different problems. And one of the neatest things is being able to engage with that client, but then bring all the options of solutions that eTech provides. So I get to deal with cybersecurity over here and robotics over here and data lakes over here. And sometimes they blend together. sometimes they're very isolated, but that diversity is one of the coolest things. Now how do you get all that into yeah, ⁓ is a mini-series now. ⁓ but you that is is one of the most unique things about ⁓ my role what e-tech provides. that make it so valuable and so much fun. But how you articul how you bundle that and articulate it is not easy either.
Jackie Slaght: no, as as someone who came into this ⁓ into this role in marketing from a completely different industry, it is a lot to learn, but it's very exciting and very cool. And one the reasons I like doing this podcast, I get to learn and talk to ⁓ all types of all different people in our company and learn a little bit. Yes, it's ⁓ never the
Wayne Hansley: And it continues to and it can And it changes and grows every day too.
Jackie Slaght: All right, well that that is all the questions I have. I won't just wanna thank you, Wayne, for being my co host today. And Brian, thanks for sharing some insight and knowledge with everyone. and and just yeah, thank you guys.
Wayne Hansley: Enjoyed it. Thank you.
Brian Gifford: Had a great time.