Video: Build a Unified Monitoring Infrastructure in Energy and Utilities for Uptime and Audit-Readiness | Duration: 3608s | Summary: Build a Unified Monitoring Infrastructure in Energy and Utilities for Uptime and Audit-Readiness | Chapters: Welcome and Introduction (0.56s), Speaker Introduction (41.25s), Monitoring Decisions (488.33s), Technology Problem Areas (739.785s), SolarWinds Solutions (997.05s), Activity to Evidence (1273.005s), Implementation Strategy (1337.9s), Dashboard Demonstrations (1758.31s), Outcomes and Proactivity (2210.02s), Compliance and Auditing (2277.435s), Closing Remarks (2601.13s)
Transcript for "Build a Unified Monitoring Infrastructure in Energy and Utilities for Uptime and Audit-Readiness": Hey, everybody. Thanks for joining us for build a unified monitoring infrastructure and energy and utilities for uptime and audit readiness. Just a few housekeeping items before we start. We'll also give everybody a couple of minutes. This webinar will be recorded and provided to you after via email or some other notification. So we'll go ahead, wait a couple minutes, and wait for people to come in. Cool. I think we've got enough people. Scott, do you wanna go ahead and take it away? Hello, everybody. My name is Scott Pross, and I am the principal solutions strategist for SolarWinds. Today, we're gonna be talking about building a unified monitoring infrastructure for the energy and utilities, vertical markets. I'm really excited to be here. My background, I've been doing SolarWinds for about twenty years. I learned it when I had to build a billion dollar knock from the ground up using the product. I had a 99.99% customer facing SLA. So that gave me four minutes and thirty seven seconds of downtime a month for 33,000 devices in 40 different countries and a 180 different data centers. So a lot of experience with the product. The last ten years after being a customer of SolarWinds for ten years, I worked on the professional services side, and I worked in a lot of different, verticals, everything from, DOD and classified environments to commercial to, energy and utility, companies and and public utilities. And I've seen a lot, and I've done a lot with SolarWinds, and I'm hoping I can, share with you guys some of the, insights that I've gained just, you know, from the the last twenty years of, you know, how to get the most out of your observability platform and how to really help you guys, figure out what is the best way to move forward as well as what's the best way to utilize this huge platform that we have with so many different features to really be able to get, the most information about you... About these environments. You know, these environments are very different than most other environments that we see from a lot of our commercial customers. You guys are dealing with SCADA. You're dealing with a ton of compliance rules. You have air gap networks. You're always distributed. So these are all these different issues that we see for our utilities and our gas and energy customers. And because they're so unique, there's some very unique approaches that we can also take that are gonna make things easier for you. And, hopefully, we can, I can share with you some of of the things that didn't work for me so you don't fall into those same pitfalls along the way, and we can really help each other understand, okay? You know, we have this phenomenal, platform. The SolarWinds observability platform is is great at helping us understand what's happening on our network. But how can we get the most out of it within these verticals where, in some respects, our hands are tied. Right? There there are certain things that we just can't do because of our compliance rules, because of having an air gapped environment, because of the the distributed look of the team and or the environment just makes it so much dip... More difficult. So when we're looking at the overview of our industry, electric, gas, water, all these different areas, As we talked a little bit about, some of these difficulties include that distributed footprint. Right? You have your generation, of of these utilities, the the transmission of it, the distribution of it. You have plants and substation, the pipelines. It's really crazy because it's almost like having an IT network, but actually built out physically across so many multiple environments, so many multiple locations that it... It's really difficult because of how distributed it is. One thing I've learned just from my years of working with with the electric, gas, and water companies is it's never just one location. You know? If if you have a company, a lot of times, you're... You have a single data center. You have a single, location that you're trying to monitor. With energy, gas, and utilities, it's never like that. You know, if if you have, less than 50 of them, you're lucky, you know, because it's just constantly growing and it's constantly moving. And then you also have that issue of... You've got your corporate IT, right, which is obviously important for keeping the company up and running, whether that's email or security or or your databases. That's really important, but you also have your OT. You've got your SCADA, your advanced metering infrastructures. Right? Being able to see what's going on with my... Within my OT environment. And something else that we have to remember is we don't only have in the OT environment. It's not just OT. A lot of times, we have IT environments within that OT environment. And because the IT environment lives in the OT environment, now it's gotta follow those same rules, regulations, and compliance standards that we actually have in OT. So it's not... You're no longer looking at your corporate IT environment. Now you're looking at your OT... Your IT environment within OT. So it even gets more complex. And so, because of that, in some respects, if it's not your gap, maybe they can communicate with each other. So, for example, when I do my health care customers, in my health care industry, my IT and my OT, they're allowed to communicate, and that's what makes things a lot easier for them because they can share information. They can share infrastructure and still really get a single pane of glass between them. For my electric, gas, and utilities, that's not necessarily true. A lot of times, they can't share information because they're air gapped. So you might have a duplication of what's going on, in IT, in your OT. You might have a separate email system. You might have separate databases, separate, domain controllers, those kinds of things. We see that all the time. And so that, again, makes it a little bit more, difficult. And then you have the regulatory pressure. Now coming from a background with DOD and working in classified networks, I understand this really, really well. And, you know, I used to think that, DOD was alone in how much it had. And then I started working in the electric and gas and and utilities areas, and I saw that their compliance is pretty much as crazy as DODs because it's so significant. If something were to happen in those environments, it would affect not just, you know, our company, not just our region or our country. It could have, have an effect on on the world. So making sure that we have all of these regulatory compliance standards in place for TSA, for, NIST two, for AWIA. All these things have to be in place to make sure... And the most important, it's not just having them in place. It's being able to prove that they're in place. You know, having them in place is the first part, and then actually making sure that we can show an audit trail of everything that we've done and that when we do get audited, we can come in and we can say, hey. All of these things are in place. They're working. We have to be able to prove what we've done and not just do it. So it's really a two step process here. It's making sure that you're in compliance and then proving that you're in compliance at the same time. So, and those are two different things. You know? We... You you might be using the same part of SolarWinds to do it, but you might have set up SolarWinds perfectly to have all your compliance rules in place. But now when the outside auditors come in, you've gotta go ahead and prove that to them. And we're gonna talk a little bit about how to do that as well. So what's driving our monitoring decisions? Well, there's a lot of things. Obviously, incidence is number one. Right? We wanna make sure that we've got our entire environment covered so that we're able to control these incidents. Be proactive so we can avoid any incidents, but also be able to react appropriately when they do occur. And we're gonna talk a little bit about what does that look like? How are we able to, display information in such a way so we're able to to to react when we do have problems? Of course, you have your audits. You gotta make sure that your your your compliance rules were in place, and SolarWinds is great at helping you set up the things for backing up, your configurations, for making sure... Reporting on your your issues, keeping logs, all those things. It's a really big help for being able to adjust, for for your audits. So we're gonna talk a little bit about what does that look like? What does that look like from a reporting standpoint? How can Solver has help me report, you know, what I've done? I wanna show people what I've done. I wanna show people that I've been successful in implementing all these compliance standards. And now it's just a question of saying, hey. I I I need to be able to show that. And SolarWinds actually is very good at doing that. And then cloud and hybrid modernization. And and you might not be talking about cloud because, you know, you might be in an air gap environment that doesn't have cloud access, and that's okay. But we're constantly modernizing. We're constantly switching out, you know, new technologies, adding new technologies into the environment. And because of that, we need to make sure that we're able to monitor that new technology, that we're able to correlate that new technology with what we're seeing, and even correlate how this new technology is behaving as opposed to how the previous technology that we're using was behaving. I wanna be able to show a return on investment, you know, that, hey. This is what my old system was doing, and this is what my new system is doing. And I'm seeing that 20% increase in resources and speed that I expected to see, when I when I made that purchase. And then you have your mergers and acquisitions and new sites. You know, one of the things I say about electric, gas, and water is it's constantly growing. It's constantly improving. And companies are buying and selling each other, you know, quite a bit... Quite frequently. And so when you do go through a merger and acquisition, it's seeing, okay, what are they using over there? What ideas are they bringing with them? What technologies are they bringing with them? And do I have what's necessary to be able to monitor all of these new sites? Do I need to purchase something new? Do I need to go back and re architect how I'm doing all of my different, my my different monitoring, dashboards and alerts? Because they might have something different that I'm not used to monitoring, in my current environment. So we see that quite a bit. And then not consolidations. Consolidating all of this into a single place where all this data is coming into. And and, you know, you're drinking from the fire hose here. The amount of data that's coming in, we're gonna talk a lot about this. How do I create dashboards that are clear, that are easy to understand, so that we're able to make decisions based on this data? You know, you're... As I said, you're drinking from the fire hose. The amount of data coming in is enormous. And so being able to sort, filter, and get the right information in front of the right person is absolutely key. One of the things I I I do share with a lot of my customers is my background is not actually in IT. It says a licensed psychologist. And the reason that I share that is because one of the things that's really important is, you know, I think of observability as a big behavior modification platform. You know, the goal is to get the human to take the right the right reaction or or react correctly to the environment. But the most important way of doing that is to put the correct information in front of them to do that. So we'll talk more about that as well. So when we talk about our technology problem, well, you know, there there are so many that we deal with, but we kind of broke this down into four different areas that that make a lot of sense. First, we have your blind spots before the call. So, you know, before you get that call from the customer or the user, you know, you're you're you're doing your normal stuff. You're paying your devices. Right? You have your interface information and your your, your disk service information. All this this different kinds of information is coming in. Right? But we also need to be aware of what aren't we seeing. And every environment has got blind spots. Okay? They... You know, we just can't cover absolutely everything. But it's important that we've identified those blind spots as well. So we understand that, okay, this is what we can see, but just as important, what can't we see? So understanding our gaps and our blind spots before the issue occurs and being able to remember those as we're actually trying to troubleshoot is key. Because if one of those blind spots is involved in the actual problem, And we have to be aware of, hey. We may not be getting the correct the correct or any telemetry from that part of the system. And then slowing the investigation. You know, I always tell people that MTTR, the mean time to resolution, that is so important because being able to correlate all this data together. So we're losing time in searching across all of our different tools, our different consoles, our logs, our vendors. You know? And then you have a handoff between your knocking, your infrastructure, and site teams. And so getting everybody on the same page is difficult, especially when all of these teams and many of these teams have their own tools. They have tools that they absolutely love, and I get it. You know? I've had tools that I've grown up with utilizing the last twenty years, and they're great for me, but it doesn't give insight to my other team members. And so they can't see necessarily what I'm seeing, and they may have information that I also need. So to be able to to take all of this loose data that's that's spread across many teams and many vendors and many tools, that will really slow down our ability to actually resolve the problem quickly. We also have our audit, evidence gaps. You know, the auditors are gonna ask what's changed, when did it change, how did it change, was it approved, was there a CDE, was it fixed, you know, putting all these things together. And we now need to be able to show that we've done this. We need to be able to show that I've patched that, CVA. I've, resolved that issue. I'm backing up this data. All of those different rule sets from the compliance that we were talking about before. Even if you're doing it, you still need to prove it. You know? And that's key as well to our success, and it's it's gonna fall on us to do that because we understand the environment. We understand what we're monitoring. We understand what we're observing. We understand what's going on within our SolarWinds platform, and so we now need to be able to pull that data out and prove it to somebody else. And then finally, you have your data controlling your growth. You know? Sensitive telemetry that can't leave the environment. You know? You have new substations coming online and sites that's raising your your your no count. You know? You've got exposures here. And, you know, the most important thing for us is making sure that we are secure. We need to keep our environments as we grow and we're dealing with more and more data. You know, it's so easy sometimes to get caught in that trap of, oh, we'll just do this because it'll give us access really easily. We can't do that here. You know? And, I see that a lot with my commercial customers. Well, we'll temporarily just open it up so we have access. That's not an option for us. And so because it's not an option for us, we need to make sure that as we're building this out that we're, you know, talking about, okay. We're gonna be adding new environments. We're gonna be adding substations. The data's gotta stay where it is, and we gotta make sure that we're secure with it. And so, you know, these are four areas that we have to work with all the time. Awesome. Cool. Well, it looks like we've reached a poll question. We'll give the team a couple of minutes, to take a break. And then while we take the break, go ahead and answer that poll question, and we'll get back started in the next maybe fifteen to thirty seconds. Alrighty. I think we're just at about time. If you can complete the poll question if you haven't, go ahead and do that right now. Scott, go ahead and take it away for the rest of the presentation. Awesome. So we... We've we've seen what the problems are. How can we help? And we're gonna break this next part into a couple different pieces. The first part, we're gonna go through some slides talking about how we can help and kind of show you, some some different things that SolarWinds can do. But then I'm gonna take you through a demo because I really want you to see how we... You know, what it is that we're doing in this area that can make things so much easier for you. And we're gonna break that into two parts. We're gonna look at dashboarding, and we're gonna look at compliance as well. So, really two exciting areas that we can we can make a difference here. So how can SolarWinds help help? So first of all, the best thing is knowing before the customer calls. Okay. And, you know, the perfect example I give is... And many of us have... You know, we all have Internet in our our homes. And when your Internet goes down and you need to call your vendor, you pick up the phone and you call them. And, you know, your first experience a lot of times is I'm saying, did you reboot your your modem? Did you reboot your router? Have you rebooted your computer? What lights are on on there? Right? And we become the troubleshooters, like, for the vendor. But one of the great feelings that you get is when you call the vendor and you tell them, hey. My Internet's not working, and they say, we know about it. We're working on it in your area. It'll be another two hours. That gives you confidence in your vendor, and it's no difference with our customers and our users. When our customers call our help desk and our help desk says, yes. We are aware of the problem and we're working on it. There is a feeling that your customer or your user gets that they are in charge, they get it, and they're on top of it. You having to prove to them that there's a problem is never a good feeling. And that's why network performance monitoring and observability is so important because it gets us to be proactive. And while we do have to be reactive, we're aware of it before our customers and our users are, and we're already working on the problem. So these are things like showing availability and latency and packet loss. Right? And path help. Using things like NetPath and PerfStack, which we're gonna show in a little bit, to really narrow that cause down and get a really good understanding of what's happening. Okay? The other thing that's great about SolarWinds, it's... You know, so many environments nowadays are, you know, SaaS companies, and that's great. We have a we have a SaaS component too, and I love it. It's phenomenal. But we're also self hosted. Okay? We can put it behind a firewall in a in a place where you are in full control of that environment. You're in control of the operating system. You are in control of the, actual, SolarWinds environment. You can decide when patching occurs. You can decide when upgrading occurs. All of that is in your control, which is really helpful because we don't work on normal timelines. You know? We have blackout times that we might not be able to do things. So I don't want my vendor making changes or upgrading my product or patching my product even without talking to me first. So when it runs in a in a self hosted environment, you're not only in control of your data, but you're in control of your timeline. And I know that my DOD customers also really appreciate the ability to be able to say, hey. This is, you know, what I need to do, and this is when I need to do it. Now do... Can you... If you don't have an air gapped environment, can you use platform connect and share information, to to to the SaaS environment and utilize SaaS? Absolutely. And we want you to do that if it's within your compliance standards to be able to do that. But if not, you're in control, and you can take control and make sure that everything is working the way you want it to. And then finally, it's turning activity into evidence for your networks. It's your configuration history, your patching timelines, your vulnerability priorities, support, and audit preparation. It's being able to say, hey. I did do these things. Let me show you. This system has been backed up for the last hundred and eighty days without a problem, and here are the configurations to show that. You know? Here are the logs that I've ingested, that have tied things. Vulnerabilities, CVEs, all of those kinds of things to show that you've taken the proper action and that you're staying in compliance. These are all things that SolarWinds is great at doing. It's, you know, three major areas that we can really accomplish and help you succeed and prove out not only that your, you know, your team is a great team and you're really good at what you do, but here's the evidence I have to prove it. Where do we start? How how do we start doing this? First, you're gonna explore your blueprint. Okay? Connect IT networks, play at substations, remote sites. We're gonna... You're gonna choose where am I going to start? What is my my centralized areas? What what does my distribution look like? And you always start with a physical, you know, topology first, And that will help you determine what does my logical, topology actually look like. So it's it's making sure that, you know, you're placing your SolarWinds polars in the right place. Your SolarWinds application and database are living in in in the proper place. I've had people that try to separate out the... These solo application server and database server. You can't do that. Those need to live together, because they're constantly communicating with each other. And then next, we wanna assess your network. You wanna test ASH against a small sample of your network, and you don't wanna do just one... Necessarily one site. And it... It's okay if that site includes a really good distribution of the types of devices that are in there. That's fine. But I wanna make sure that I'm looking at all of my different routers, my switches, my pumps, my compressors, all of the, you know, all of those different pieces that in a real world, I'm going to have to make sure that I'm monitoring and to get just a a small smattering of that. Sometimes I tell people, choose a couple of sites. Maybe it's a couple of devices at each site. I wanna see be... How did... How having a distributed network is going to impact, you know, my environment because it's going to have an impact. Everything's not living together. So maybe it's great to pick something that's, you know, real close by. Maybe it's good to pick something that's a little bit further away. You know? Or that... I always tell people, also, maybe choose one of those one off sites. The thing that's got a really wacky thing that's in it that nobody else has, I might be curious as to how is SilverWinds gonna handle that because I wanna see the good and the bad. Because once I see the bad, I'm able to say, okay. Let me come up with a plan for dealing with this particular difficulty. So, you know, SolarWinds... I always tell people, the biggest advantage that SolarWinds has is how customizable your, it is. Okay? The biggest disadvantage that SolarWinds has is how customizable it is. I mean, on the DOD side, I'm monitoring things like nuclear missile silos, drone swarms. I'm doing underwater autonomous vehicles. These are not devices that are made really for monitoring. Just like a lot of your devices inside of the utilities and and the the gas and water, they're they're... They have monitoring built in, but they're not really made well for that. And then you wanna prove it's self hosted. You know? You wanna run your proof of value and show your value, you know, for a a a region or a regulated segment. You know? Keep your... Looking at your data flows, your scale, your evidence, and your licensing. What is it that you're going to need to grow this out to really make sure that it's going to do exactly what you need it to do? Because doing it within a bubble was nice. Don't get me wrong, but we need to make sure that we can actually cover the entire environment, you know, soup to nuts. The goal was to get down and say, this is my tool. This platform does exactly what I need it to do and be able to make sure that it's providing all the data that you need to make your decisions. Okay. So as far as technology solutions, and we talked about the gaps before, now how do we bring those into play using SolarWinds so we can avoid the problems? Right? So the the... That first gap we talked about, the blind spots before the call. Right? And continuously having health techs, having information, coming into the NOCLIS, tracking latency, packet loss, throughput, interface information, hardware help, making sure that you're alerting your thresholds are set up before the customer notices. You know, this is a big thing that, hey. Maybe you know that things are gonna go... Be a problem at 80%. Maybe you set yours for 50%. You know? I always tell people, the SolarWinds environment's set for two standard deviations, for a threshold automatically and three standard deviations for critical. You know? Does that number work for you? If not, it can be changed. You wanna find what works for you and your customers and your users. Okay? So on the next one, slow investigation. This is the one that we talked about. It kills you. What's great here is everybody's using the same platform. I'm seeing their data. They're they're seeing my data. But more importantly, SolarWinds is seeing everybody's data. So it's gonna be able to look and say, okay. I've got a problem over here. I've got a problem over there, and I've got a problem down here. This is what they have in common. This is where you need to go to solve your problem. That's going to, you know, bring down your your MTTR in a really big way because now SolarWinds is able to tie this data together for you and point you in the direction to say, here's your issue. This is what you need to do. Here are the steps you need to take. Then you have your audit and gap, your your gap evidence. Right? Or your evidence of gap. So, an automated exportable evidence shield, being able to run reports to say, yep. I backed up all of my devices. Yeah. I'm following all my password rules, my patching rules, being able to show that in a report that's running constantly. One of the great things I... That I love to see is when my customers say to me, hey. I got audited last week. And the auto came in. He told me what I needed. I went into SolarWinds. I ran the report and printed it out for him, and the guy didn't bother me for the next two weeks that he was there. He was dealing with everybody else because my stuff was all done. And SolarWinds makes that really easy to be able to do. And I really like having that feature of being able to say, hey. Give me a report of where I stand right now in compliance because SolarWinds is aware of what your compliance rules are. And then being self hosted and scalable with monitoring. You know, keeping your telemetry and your processing inside of your perimeter. As much as I love SaaS, right now, we're not at a point with a lot of our companies, like our our gas and our energy, where we feel comfortable letting any vendor have our data. And, you know, for DOD, it was the same thing. They won't... Don't want the vendor to have the data. They wanna own it. It wants to be theirs, and that's great. We have that capability. As we do move forward into those environments where we feel more comfortable, we're gonna also be able to do that. We're gonna be able to say, hey. Let's bring in SaaS where we feel comfortable, you know, and if that day comes. So you're gonna have that hybrid ability to be able to be in both areas. So next, I wanna really start demoing and giving you guys an idea. What does all this look like from a dashboarding point of view and from a compliance point of view? What... You know, how do we accomplish this? And this is where the rubber meets the road. Right? Because vendors are gonna tell you all day long about how to use your software, and they may even show you a demo of it. But is it something that's unique? Is it something that's going to make my life easier? Because if it's not gonna make my life easier, I am not interested in it. If it... If it's something that, you know, you can do but isn't realistic or isn't gonna provide me value, yeah, I'm gonna skip it and just keep going on what what works for me. Right? So the demo that you're about to see, we're gonna start off actually in a different way. We're gonna start off with creating a dashboard for the nontechnical user. Now people say to me, why would you ever do that? Well, the reason I do it is simple. A, I wanna make sure that my executives and my leadership know how good I am at my job. That's really important. You know, I can tell tell people my SolarWinds dashboards. They are my performance review that happens every single day, and it reminds them how good my team is at what we do. And I wanna prove that to them. I also want the users to be aware of what they can do, what they can't do. Right? They're out there. They're trying to do their their jobs every day. I wanna make them aware of any issues that we're having so that they can take backup processes. But more important than that, I also wanna remind them how good we are at our jobs. You know, one of the things I always laugh about is IT and OT people are really good at high fiving each other when we're successful. When we do something cool in the in the environment, we'll high five each other, say, hey. Check this out. We'll share it to each other. We never share with the nontechnical people because they don't understand it. They're not gonna understand how cool it was, so we don't even bother sharing it. And at the same time, you know, we... I wanna remind them that, hey. We really are very good at what we do. And so we're gonna start off with that dashboard. I'm gonna show you a dashboard that is built for leadership or for a user that knows nothing about technology. Okay? They know they needed to do their job, but they don't know what it does. Now they can look at this dashboard here, and they can immediately see what is the status of, you know, their environment. Is the SAP ERP system working? The maintenance and and work orders application, you know, the production hydrocarbon accounting application, the energy trading risk management software, email, you know, all of these different pieces that they need to do their job every day. But this dashboard actually does two things that most dashboards can't do. First, this dashboard's only gonna turn yellow or red if the issue is customer or user impacting. In other words, I don't wanna create fear or confusion among my customers or my users. So if I have a web server farm of 10 web servers and I lose a web server, this board... This dashboard is not gonna turn colors. They don't need to know that. Okay? Now I lose eight of those 10 dashboards. Yes. This is gonna turn callers. It's gonna say, hey. You're having a problem with email. Don't email, you know, the the land, at least team about a problem or, your your safety team about an issue. Pick up the phone and call them. Right now, email's not... Is having an issue. The second cool thing about this dashboard is this dashboard is actually used by you, the engineer, as well, but you're gonna have access to things they don't have access to. So, for example, you're gonna be able to click on this performance analysis down here where we see the email's having an issue. So this is going to take you to another screen that's going to take all of your email components and tie them together on a single pane of glass. You're gonna be able to see your networking information, your application level information, your server information, your virtualization information. Remember, this is on the IT side of things. So being able to see all this data together is absolutely key to our success. You're also gonna be able to click on this icon down here. This is gonna take you to a live SilverWinds map of that email environment, of that IT environment. It's gonna show you who's having problems communicating with who. But more importantly, it's gonna show you on which layer. Is it happening on the storage layer, the database layer, the application layer, the network layer, the server layer, or the virtualization layer? Now you know which team or teammates you need to get involved. Now I'm gonna be honest with you. I can't undervalue the the value of this particular dashboard and this particular screen. Because one of the things that I learned having four minutes and thirty seven seconds of downtime a month is I had exactly zero seconds to spend arguing over whose problem it was. This dashboard solves that problem for you. It says, hey. We have an application level issue. All of the teams can see that. Okay. And now the application team come in here, and they can click here, and they can get email level information on what's going on on the... From the application point of view. And now they can take action to resolve that. So this is great. This is our IT side. This is what we love to see. Right? We enjoy seeing our IT side. What about the OT side? Right? Well, the OT side is very similar. It's gonna look a little different, but it's gonna feel the same. Again, being able to have that same look and feel and being able to spread that across our OT and our IT so that we can share these kind of this kind of information if we need to and everybody understands. So here, we're looking at our production SCADA environments, our distributed control systems, our terminal and tank, you know, field connectivity, pipelines. You might might have substations on here as well. Our safety systems, our compressor, and our pumps, all of these different things that are absolutely important for us to make sure are up and running. And, again, if there's a problem, we can click on that performance analysis, or we can click on a map. And now it's gonna take us to an OT version of that map. You're gonna see your different pumps. You're gonna see your network switch. You're gonna see, you know, is this... Is the the PLC the problem? Is the is the station HMI the problem? Is the control center uplink the problem? And, again, once we've identified that problem, that team can be contacted. So I don't have to worry about it be... You know, contacting the network communications team, you know, or the the the the mechanics for fixing up the pumps. I know I have an HMI system issue, and we can click into that and get that team. And sometimes it's the same team, and sometimes it's completely different, and that's okay. But at least they know where do I need to go, who do I need to send, and what do I need to do? And those are the questions that we always wanna answer. Now I wanna kind of, go back a little bit as we go here because I wanna talk about... You know, we've we've looked at a lot of different information here. Right? And that's good. And it's it's really important that we see all this. But all of this really comes down to one word, and it's actually the most important word when it comes to observability, especially in IT and OT, and it's also the word that we forget about the most. Okay? And that word is outcomes. And I'm gonna prove it to you. Okay? I'm gonna use a little bit of satire to do it. I'm gonna take you over to my Star Wars dashboard. So I want you to think back to the movie Star Wars. So in the movie Star Wars, if the Death Star had a NOC and the NOC was running SolarWinds platform and SolarWinds observability, this would have been Darth Vader's executive dashboard. Okay? Now think about this. He would have known when the tractor beam went down, or the detention center cameras went offline, or the trash compactor stopped running. And think about how that would have changed the story that we all know. He would have had information of being able to react and be proactive and make decisions based on actual information within his environment and being able to make those decisions. Because I always tell people, it's not if something's gonna go down, it's when. And being able to control, you know, how you have to react and having that information is absolutely key to our success. So we've kinda talked about the dashboarding piece, and and that's all really cool. I wanna move on and and speak a little bit about the compliance piece because that's the the difficult part. You know, I I always said everybody really enjoys the dashboarding and looking at the information and all that. The compliance part and and the auditing piece, that can... It could be a lot of work to put that all together for a lot of people. And it's kind of the unsung heroes. Right? It's all happening, and it's all working, and I can prove it all, but, you know, nobody's seeing it regularly. So I'm I'm gonna dive into our observability self hosted demo, on on our our website. And this is available to everybody. So if you are interested in this and this is something that you wanna take a look at, you can. Because if you come over here and you look under our network configuration area, we we can go into our compliance area. Now a lot of these compliance rules are going to be made for different verticals. And if you have a THWACK account, which I, would strongly suggest that you do, THWACK is our customer supported forums, where our customers share different information. Now let me tell you, our gas utilities, water customers are some of the best, content creators there. They do a great job of creating content that others can use, especially when it comes to reporting. Right? So people have created these reports for you. You don't have to go in and recreate them. They're already there for you, and you could pull some of these down and just, you know, maybe tweak them a little bit so they work right for you. Sometimes they don't even need to be tweaked at all. They're exactly what you're looking for. So I want you to be able to use those. So, you know, when it comes to our policy reports, our policies are actually broken up into three main areas. You you really start with your rule set. So these are the individual rules. This might be, a password rule that... For your NIST two compliance. It could be a password expiration rule. It could be, an SNMP, string rule. You know, all these different kinds of of rule sets that we have to follow based on all these compliance rules. Rules. Now these rules are all tied together, and they make up a policy. Okay? And that might... You might call... Have one that's called your, network, password policy or logging setup, you know, all of those. And you take these policies in and you tie them to your devices. So you might have a bunch that are tied to your Cisco switches and then then some that are tied to your your routers. And it might be vendor specific. Maybe you have different rules for different vendors even. And you can create these rule sets that SolarWinds will make sure is being followed. Now how do we do that? Well, we do that several ways. One way is when we we back it up every night, we're gonna review those backups, and we're gonna run these rules and these policies against those backups to see those configurations, to see are they actually following it. We're also looking for real time. You can remember, you could send SIS logs so that we have real time change detection. So if somebody makes a change to, you know, one of your configurations, we can not only be alerted on it. We can see, is that part of our compliance policy? And if it is, we can actually change it back and say, hey. This wasn't an authorized change, and it takes us out of compliance, and we could put it back into compliance. That is a huge help. So to be able to say, hey. I don't have to worry about it because if somebody makes a change, SolarWinds is gonna put it back to the way it was. That is huge to be able to do. And so once you have your policies, then you get to your reports. Right? Then you're able to see your different reports and your reports that you can then run. So you... When you click on one of these... So as we talked about, IT lives in OT. So here's an, set of IT rule sets that you may have for your Cisco devices, and now you're able to see what's in policy, what's out of policy, any problems that you have, and if so, at which locations. So you're able to actually go through and see which devices are giving you a problem as well as, you know, what the issue might be. And so you're able to get more and more information on it. So taking this information and being able to provide this to an auditor is so wonderful because it makes your life so much easier. So if you've already got all of this information in there, if you're already, you know, doing your backups in here, you've got your compliance rules in here, Now it's just a question of building out these reports. And as I said, you wanna rely on FLAC. FLAC is a wonderful resource for us to be able to go there and see what others are doing and what others have done, and they're... Them sharing that information is really, really nice. And you can... If you need to sneak it in and and have your security team vet it first, it's just an XML file. So it's really easy to see what they're doing. You can then import it into your environment, and now you've saved yourself, you know, hours, sometimes days of of of work to get these compliance standards. So I think we've kind of taken taken everybody through a really nice process here. We... We've seen, you know, what are the difficulties of dealing with, you know, oil, gas, water utility environments, really being able to see where are, you know, where are my issues? Where do they lie? What are our difficulties? Because as I said, our difficulties are different than a lot of our commercial customer, difficulties. Okay? And then the other parts are understanding what our gaps are and our compliance issues and how do we, you know, take this information and make sense of it. And I think by showing you guys these dashboards as well as all of, these compliance options that we've got to move forward and to tie everything together, we're gonna empower you guys. And that's really the goal, to empower our customers and our users to take SolarWinds and do things with it that are go... It's gonna make their everyday lives better. And that's really our goal. And whenever I'm doing this, I'm always trying to improve the lives of our IT professionals, but also, you know, our our our users that aren't in IT. I want them to share and understand what's going on within their environment too. And we can tie all this data together so it all makes sense. So really appreciate everybody joining us today. If you have questions, please put them in the chat. We wanna answer those questions. If there's anything that we need to take offline, we will. I'd love to hear from you guys, about what you're doing in your environments right now, any difficulties you're... That you're having or... And your success stories. I wanna hear about what have you guys done successfully. These environments are ever changing, and because they're changing so much, it's it's difficult to stay on top of it. So I wanna learn from you guys as much as I can I can teach you? I wanna learn from you and see what you're doing as well. Really appreciate everybody joining us today, and, hope you have a great day.