Skip to content
Episode 6: Risk-Based Cybersecurity with Clint Bodungen episode artwork

Dec 19, 2017 36 min

Episode 6: Risk-Based Cybersecurity with Clint Bodungen

from Pipeliners Podcast Hosted by Pipeliners Podcast

Do you want to feel instantly smarter? Listen to ICS cybersecurity guru, author, hacker, and educator Clint Bodungen talk to Pipeliners Podcast host Russel Treat about the latest cybersecurity issues and threats affecting the pipeline industry. Learn about the history of cybersecurity, threats that involve national security, and the rapidly-changing technology that helps assess new and unique threats to know how to react in each situation.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Episode 6: Risk-Based Cybersecurity with Clint Bodungen

0:00 36:20
of matches

Transcript Auto-generated, may contain errors

This is Russell Treat. Welcome to the Pipe Liners Podcast, episode number six. The Pipe Liners Podcast. We're professionals, bubblegeeks, and industry insiders share their knowledge and experience about technology, projects, and pipeline operations.

And now your host, Russell Treat. Thanks for listening to the Pipe Liners Podcast. We appreciate your taking the time to listen to this episode and to show our appreciation, we want to let you know about a signature prize pack. We are offering a free, customized Yeti Tumblr to one listener each episode.

How do you register to win? Simply visit pipelinerspodcast.com slash win. That's pipelinerspodcast.com slash win. Do you know yourself in the drawing?

This is our way of saying thank you for being part of the audience. Well today we're very fortunate. We've got with us Clint Bodungeon. Clint is a cybersecurity ICS guru.

You may have heard his name in an earlier episode with Will Gage because he came up in the conversation. Clint is the author of a book on ICS Cybersecurity. He's a hacker. He's a teacher and educator.

He teaches with gas certification Institute and the cybersecurity part of our Skate of Fundamentals. Really a fascinating guy to talk to. So with no further ado, let me welcome Clint Bodungeon. Thanks Russell.

Hey Clint. So how are things? How are things going for you? Busy, busy and I think that's a good thing.

By the way I just want to say I think in the 10 years or so that I've known you that's the first time you actually got my name right. I've got a complex last name so it's okay. Well it also is not exactly, I mean it's pronounced exactly the way it's spelled but for some reason you don't want to do that. So there you go.

Well if you go to Germany and then tell them that they'll say I'm pronouncing it wrong so it's fair game. Several things I wanted to visit with you about, I mean we've had the opportunity to work together on a few projects and do some interesting stuff. I think one of the things that I'm always fascinated about working with you is kind of how you just approach this whole idea of ICS cybersecurity. Maybe we could, we'll start by talking about the risk-based approach that you advocate to cybersecurity.

Can you tell us what that is, what it's about? Sure. Having been involved with ICS industry and I think it's funny that ICS is actually an acronym that just kind of recently came about back then it was just control systems and I think for a long time the SCADA was the acronym. But you've got all these different acronyms out there to describe control systems and throughout the years there have been a lot of concepts about security that have come and gone with the convergence of control systems with traditional corporate systems brought the need for a lot of security and it's kind of an old story by now.

But there's a lot of disagreements in the industry about whether or not there's a need for cybersecurity and ICS how much. There's pretty much a huge dichotomy about the philosophy of ICS cybersecurity. And one of the aspects that I think has gotten lost over the years is the risk-based approach and when we say risk-based approach, we're not doing cybersecurity for the sake of cybersecurity, we're not trying to impose cybersecurity into control systems but we're focused on risk and it just so happens it's a cyber element to risk. For example, when we think of control systems, there's been hazards analysis and has ops done in control systems for decades and that is essentially the risk analysis and the risk assessment for control systems and now with the convergence of cyber into that, you're adding a new element.

So there has to be this this cyber piece to that but all too often we see people trying to impose cybersecurity into ICS as a separate element and it really just needs to be kind of part of something that looks similar to the has-ops. And so I think in the control systems we're really primarily concerned about reliability, efficiency, production and safety and those things that are that are native to industrial control systems and anything that threatens that is where our risk is. And so ultimately we want to identify one of the things we really want to know. We want to know where is our risk or what is our risk.

We want to know what's the likelihood that risk can be realized. We want to know what is the potential impact of that risk and then ultimately we want to know how do we manage that risk, reduce it or eliminate it if we can with the resources that we have available to us. And that's really it's not so much that we want to do cybersecurity for the sake of cybersecurity. We want to protect the things that are dear to us and control systems that's reliable, efficient production systems and safe systems.

I think that's right on target. In fact, I think that's one of the things I like about the way you approach it because to me, for the pipeline world, it's all about risk. We as pipelineers, we only get our name called. We only make it into the media if we have a mistake or an error.

Our job is to reliably and accurately move product and to do that without impact to the environment or the community. So, pipelineers by their nature are really familiar with the idea of risk management. I mean, you'd have the same approach being applied in leak detection. There's actually some new API standards that are out that are addressing a risk management approach to pipeline safety.

So, to me, the idea of taking risk management and applying it to cybersecurity for the pipeline is just another aspect of something that might be a threat, that might cause an issue or a problem where we're not able to operate reliably. What I see though in a lot of risk management functions and organizations is the kind of thing that once a year or once a quarter, we go around and we look at the risk and we write that down in a book, but it doesn't necessarily change the way we operate or change what we're doing. I'm wondering, did you comment about that? One of the things I know about cybersecurity is the risk changes quickly.

There's two or three fundamental mistakes that people do when they're looking at risk. And this is not only just on the ICS side, but also from the cybersecurity side, the corporate business side. But I think we really need to look at it from an ICS perspective, if we're going to do risk assessment or risk analysis properly. And the first is the data that we're coming up with, for example, one of the problems I see is the typical risk assessment frameworks from like ISO 27005 and then the NIST standards, NIST SP-830-37-39.

And they all seem to have the same concept of, on one side of this heat map, you have a number that represents likelihood and another that represents impact. And even if you look at the CISSP model where you're looking at the annual rate of occurrence, as a kind of likelihood thing, it doesn't matter if you're talking about the CISSP model or the NIST model or the ISO model, they're all coming up with these speculative numbers. We have no way of really knowing likelihood of this impact or this attack happening or this incident happening as a one or a two or three or four, because it's not attached to any real data. And so that's one mistake.

And that when you're doing your risk assessment, you have to attach actual data to give real value in numbers to your attributes, like likelihood, so that there's something real and that you can actually use to discern the likelihood of one threat over another. And we can talk about what that looks like in a bit if you want, but that's one mistake is that you're using speculative numbers. If you're using speculative numbers in a risk assessment, then it's pretty much useless. Now, going back to what you said about the timing and that's kind of the other mistake that I see is people tend to treat risk assessments as this one off thing.

Like you said, we're going to evaluate our risk and then see what we need to do about it and then put it down. And risk assessment needs to be a constant procedure, constant behavior. It needs to be always on. And a lot of people do this.

You have these little mini risk assessments. Anytime, anytime in your environment changes, you should be doing some sort of risk evaluation or risk assessment or analysis on that change. Now, there's lots of different ways to do it, which probably go way outside the scope of this podcast due to time. But again, even those little risk assessments, they still have that mistake of having speculative numbers.

Again, we can get into that if you want to, but those are kind of the two areas of mistakes that I see. So you need to have real data that can give you real results, and it needs to be an always on type of thing. What that brings up for me, and we've talked about this before, but it's the idea of a risk dashboard. What is my risk at this moment in time, given data that I'm looking at and analyzing?

One of the things I think that's unique about cybersecurity, and particularly ICS cybersecurity, is achieving something like that would seem to be possible. When you're talking about integrity management, pipeline systems where I might run a tool through a pipeline segment once every six months or once every several years, that's not real time. But what we're talking about with cybersecurity is I might actually be able to do risk in real time. That makes sense.

Do you see it that way? Or do you think we're headed that way? No, absolutely. In fact, one of the reasons why risk assessment in a risk-based approach has been left in the dust to trendier and sexier buzzwords is that everybody use risk assessment as a thing that you do initially and upfront, and then you figure out your gaps and you close your gaps, but then you get into things like threat monitoring and IDS and intrusion detection system.

People view these as inherently two separate concepts when in fact done properly, you should be using the same data points in your risk assessment to perform an element of threat modeling. By the way, threat modeling and building these threat models and risk modeling is how you add real data to those likelihood attributes to your risk model so that you're using something discernible. So using threat intelligence and threat modeling to enhance your risk assessment. But at the same time, if you want it to be always on, the data points that you use in terms of your monitoring and your threat detection and intrusion detection system, those data points are the exact same data points that you would use in threat modeling.

Thus, you should use those same data points and your risk assessment. So it's not different. You should actually use them the same. So you have in the same data points you use in a threat monitoring system or a intrusion detection system in threat hunting and threat intelligence to input into a risk assessment so that you have threat modeling and real time threat modeling and threat monitoring data into your risk assessment is how you give your risk assessment real usable data and how you make it always on.

And that is that you're right, Russell, that that's something that you would correlate into a dashboard or a sim or something like that. And we are starting to see certain technology out in the industry start to do that as companies are realizing that they can use threat monitoring and intrusion monitoring type data to be sort of this always on risk assessment. And a lot of enough, seeing the buzzword out there, some people are starting to call it risk intelligence. I mean, it amazes me, Clint, every time we talk, you drop something on me that's brand new that I haven't heard yet.

It's one of the reasons I like visiting with you. I always feel behind when I'm talking to you. It's just a situation. Well, to be fair, I think I make some of this up.

Well, you know, if you make it up and then everybody else is talking about it later, that's called inventing, right? At least trend setting. Oh, there you go. There you go.

So we were talking as we were getting ready a little earlier about this one of these topics that you see is really hot right now, which I think ties to what we're talking about, which is this idea of situational awareness and anomaly detection. So what do you see going on there and why is that a hot topic? This is a good segue from where we were talking because I mentioned this earlier in that the things that we've referred to as kind of basic blocking and tackling your proactive defense. It's lost its luster.

People don't focus on that so much anymore because it's not sexy. It's not cool. It's not trendy. And they're moving on to the shiny or buzzwords, right?

And for a while there, it was asset identification, which is still a thing, but then that's moved into you take asset identification and you combine it with threat monitoring and you get situational awareness. And that buzzword came out about a year or two ago. And then now all of a sudden, you're going to take that situational awareness and you're going to add some AI, right, artificial intelligence. And now you're going to make a nom, you're going to use it to detect anomalies.

And now you're going to have anomaly detection. And so everybody's trying to find the next biggest better mousetrap. To me, this is the equivalent. Now granted, there is a time and a place for threat monitoring, active monitoring, and the jury's still out on anomaly detection.

I'll talk about that in a minute. But by chasing this and focusing so much on this, it seems like the industry has basically done the equivalent of saying, well, I got this brand new house, an or an old house, you know, it's too hard to build a fence and it's too much trouble to remember to lock the doors in every single window. So I'm really just not going to worry about my fence or lock in my doors or my windows. And I'm going to rely on my burglar alarm to tell me when there's an intruder instead of trying to prevent the trigger from coming in.

I'm just going to let my burglar alarm tell my windows intruder. And then I'm going to make a quick rash decision on how to respond to that. And that's kind of what I feel like everybody's kind of doing with anomaly detection. There's this new burglar alarm out that's really hot and sexy, so I always forget to lock the doors.

The problem with the anomaly detection is that like I said earlier, it really is an unproven industry. We've got more than 20 startup companies that have entered the market under situational awareness and anomaly detection in the ICS industry. And Dale Peterson put out an article on, I think it was on his blog or maybe in LinkedIn talking about all these different anomaly detection companies. In fact, at S418 in January, he's having a quote unquote, bake off.

And he's basically told these companies to put their money where their mouth is. And look, prove that you can do it. And the reason why is because there are a lot of people out there that just don't see anomaly detection as a real viable solution at this point, because it's unproven, even though there's been millions of dollars invested in it. And ultimately, and I'm going to get in trouble for saying this, I probably shouldn't say this on a podcast, but I was going to write a white paper on this anyway.

So I'll just tell you I'll give you the exclusive of the hear Russell. Okay, you heard it here first, that's the first exclusive drop on the pipeline podcast. I'm actually I'm releasing a white paper soon. And I'm actually my next book is actually on this subject.

And so what really happened and when this market dropped into the situational awareness topic, the NSA released Grass Marlin. And Grass Marlin is a Java based but yet open source tool to help asset owners identify their IP based assets. And it does it passively. And so originally the first passive asset identification tool and kind of anomaly detection tool originally came out forgot what the date was, but it was released by Idaho National Laboratories or ICS cert under the name of Sophia.

And then Mike Asante carried that concept onto next defense when he left I know and founded next defense. And that was really the kind of the first concept of passive asset identification from an ICS perspective. And then years later, that's when the NSA released Grass Marlin Grass Marlin is a little bit different look and feel, but under the hood, it still has the same concept. It has the capability of parsing industrial protocols, certain industrial protocols, and identifying your ICS assets and a certain level of net flow or directionality and give you a little bit of situational awareness that's all open source.

And all of a sudden, you know, you start having all of these situational awareness companies popping out. And if you really look under the hood for the most part, all these companies situational awareness and a basic concept does the same thing. And if you look closely, all of the source code from Grass Marlin and what Grass Marlin does is exactly what all these other tools do. Their differentiator is a little bit of secret sauce and a little bit of their guess what Russell, their dashboard.

So the differentiator is how they do their visuals and their dashboard, a little bit of secret sauce, and their correlations and their in the way that they're the correlations and how they do quote unquote anomaly detection. But 75 75 to 80% of what they do is no different than what Grass Marlin can do or what NetMiner can do. One thing that we're working on is why shouldn't there be an open source solution or a cheaper solution to achieve 90% of the same thing for the industry. So that's one thing we're kind of working on right now to give back to the community is that we're taking these open source tools like Grass Marlin and NetWorkMiner and some of these industrial protocol dissectors.

And we're going to create, we're going to be releasing it early in 2018. We're going to create an open source tool and release it to the industry that will pretty much give asset owners operators a very cheap solution to get about 90% of where these commercial tools will get them anyway. Hopefully it's going to do is spawn the industry to do what Dale wants them to do to step up. And hopefully these asset owners will give consumers more than just about 10% extra secret sauce and giving them what an open source tool could really give them in the first place.

Again, it's always interesting to me about what some of the themes are around technology. And this theme about dashboards and open source tools and creating data and as you say, the secret sauce being how we present that data, I mean, that's very thematic. You've got the same thing going on in the pipeline control room about what's called the high performance HMI because everybody's trying to come up with the best way to get graphics and animations and symbology that simplifies decision making and puts context around data and makes it meaningful. I actually think that the technology is getting easier, but the understanding how human beings interact effectively with technology is getting tougher at a broad level, right?

Yeah, you're right. But I think technology is getting easier. And I think that we as humans inherently try to find a way to complicate it because we think it should just be more complicated. Oh my gosh, there's lots of truth in that.

There's lots of truth in that. Well, look, I want to segue I want to talk about a couple other things while we got you here. One of the things I want to do is talk about your book. Why don't you tell us about the book you run?

I know it's been out for about a year. I know the story from way back when you first put out the idea of writing a book called Hacking Skata. And you got some visits that maybe you didn't anticipate or didn't want, but that book actually made it to markets. So tell us a little bit about the book that you have out currently.

Okay, yeah, I'll just say I can't say too much about the old version, but yes, back in 2007, this was before this was BS before Stuxnet, right? Back then, me and a couple colleagues decided to write a book on Hacking Skata and we published a table of contents and Word got out and let's just say, yeah, there's certain certain entities in the industry that was not ready for it yet and convinced me that I should wait. Low and behold, several years later, I was interviewing with Joel Scamre. I didn't even realize who he was at the time.

The book series Hacking Exposed has been out since the 90s. It was iconic and it was the original Hacking textbook officially released. And I was interviewing with Joel and then half with the interview, it was like, oh, wait, this is the guy from Hacking Exposed and I felt like a dummy. And I actually didn't get the job, but he gave me a book deal instead.

So the job wasn't quite right, but he thought that the time was right to write an expose on ICS from a Red Team perspective. There have been some really quality books already written from the Blue Team perspective at the defensive side. Would you define for the listeners? What's a Blue Team?

What's a Red Team? What does that mean? Blue Team typically refers to the defense, the network or the computer defense, and Red Team refers to the offense. That goes back to military terminology, Red Team Blue Team or, I don't know, maybe it goes back to video games, Halo, Red Team Blue Team.

But either way, Blue Team is typically referring to the defensive side and the Red Team is the offensive side or the pretend to be the back guys. I assembled a team of great co-authors to help out and we wrote Hacking Exposed Industrial Control Systems. It was the only Red Team perspective, ICS cybersecurity book, and then a colleague of mine has since written another industrial cybersecurity book that was just released in 2017 available through Pack Publishing, my friend Pascal. I like that he wrote it because it's the second edition that I haven't written yet.

So he saved me the trouble. So that book's been out for about a year, and there is talk of writing a second edition to that one simply because, as you mentioned earlier in this podcast, security and risk move so fast that as soon as you publish it, it's already outdated. I know when we first first started working together, which was about 2007-2008 when we were putting together the Skate of Fundamentals class, this whole domain of cybersecurity, much less industrial cybersecurity was kind of wasn't really even on my radar at that time. And man, I have learned so much by listening to you teach the classes and I do the first couple of days of that class or have historically and my content hasn't changed a whole lot.

But man, yours changes every time we put the class on. So I really admire how you're able to stay current on all this stuff because I know it's not easy to do. And I think your book Hacking Exposed or the Industrial Control System is it's really interesting to kind of put yourself in the mindset of the attacker because I think a lot of times we don't do that. It's really clarifying and it certainly helps to better understand the risk when you're able to do that.

That was the whole point was that it's not necessarily there is a way and a time and a place to safely perform quote unquote penetration testing in industrial environments. But I think ultimately the whole theme of the book really is to put yourself in the mindset of the attacker to learn how to defend against them. And a lot of people would insert some su quotes here, which they're overdone so I won't do it. But you really do need to know your adversary.

Man, you were throwing in some pretty deep geeky references here, which is perfect for this group of people. I love that stuff. Well, I are one. Yeah, me too.

Bubba Geeks unite. So one of the things I want to ask you about, I had a really cool opportunity. Clint shares some stuff that he's working with me working on that is taking the software development tools that are used to create games and using it to create a training tool, an experiential training tool for those trying to protect critical infrastructure. Clint, tell us about what you've got going on in that domain.

I don't know if you're ready to share everything. But man, that is some really cool and very compelling stuff. Yeah, so we are actually about ready to come out from underneath the radar probably this week or next week. So another exclusive for you.

We'll be sponsoring the CTF to capture the flag at S4 with this technology. I need to ask you so the listeners know what is S4? S4 is one of the more technical ICS cybersecurity conferences. I like to think of it as kind of the technical, the hacker conference of industrial control systems, but it's not scary or anything like that.

It's just a very technical. Is it like industrial cybersecurity geek week? Absolutely. Yeah, it's out of all the conferences.

It's definitely one of my favorites. Dale Peterson at DigitalBine is the founder of that conference. And it's an industry favorite. And it's in Miami, Florida, at the Jackie Gleason theater, the Fillmore Jackie Gleason theater.

And it's a great time. And everybody learns a lot. Welcome for the plug, Dale. So, but what you're referring to is, yeah, we have started in about 2013, 2014.

We were trying to find ways to give better visual feedback during capture of the flag contest or just even training. It's nice to be able to look at a computer readout and see, okay, well, I've changed the coils and the registers on that PLC. Or even, oh, look, I'm looking at this HMI. And I'm seeing the water in the tank go down.

That's nice. But looking at HMI isn't the same thing as looking at a real environment. And so a lot of people are providing physical demos by getting a tabletop full of clear tanks and tubes and hooking up to PLCs. And you have a table, you have a table, a table of toys.

I'm not trying to demean that. I mean, people put a lot of hard work on that and it works great. But it has a scale and it's not a real environment. And so we started thinking of ways that we can do this.

And I had the bright idea one day while I was playing another game called Grand Theft Auto. And my character was running around shooting up this power plant. My friend looks over at me and he says, man, that would be cool if we could just, if we could do this and make it all industrial and shoot up power plants, and it was here hold my beer moment. But I kind of said, you know, why can't we?

And so I embarked on a journey to start learning how to program video games. And I found out that wasn't that difficult. There's a lot of tools that help you do this. There's some video game engines that help you.

And I discovered Unity 3D. So we started using Unity 3D to replicate entire industrial environment. And so using Unity 3D, we have two offshore platforms, two oil refineries or chemical plants. We have an electric transmission yard, distribution substations, a neighborhood, a city, and all of this stuff can replicate industrial processes.

And so anything that a plant or a process would do in real life, we can make it do in the virtual world. And using gaming engine physics, we can get pretty realistic with it. In fact, we're also augmenting the physics so we can produce a higher level fidelity of those physics. So it's even more lifelike.

And then we derived a way that we can hook up real world control systems to that. So we're essentially taking all of the digital equipment, SCADA systems, DCS, the PLCs, and we can hook that up to our virtual environment, essentially just replacing all of the physical non-digital equipment. And all the SCADA equipment can control our virtual environment just as it would control a real plant or a real process environment. So then we can start to do things like getting real visual feedback for a process like, okay, if we hack this PLC, does it really cause a critical failure in the process?

Or do we have to do more? And we can start to do things like introducing even more variables into the equation, like what if the pipes corroded? Or what if some guy stand with a cigarette or whatever? And so we can start to do not only training, but a little bit of cause and effect or a little bit of an impact analysis simulations for these industrial environments.

And then to make it even more fun, just because obviously that wasn't enough, just to have a first person shooter like environment, we went and hooked Oculus Rift up to it, which is a virtual reality system. And so now you have real world control systems hooked up to a virtual environment that you can completely fully immerse yourself into and run around a plant. Look, as a guy who has spent time building pipeline simulators and pipeline trainers, the idea that the what you're doing here is it's pretty dad gum cool. It's a lot of work to work with one of these math models, one of these hydraulic simulators and build a pipeline model and put a skater system on top of it.

The idea of creating a 3D virtual environment and then putting a skater system on top of that, what that opens up in terms of training, you know, there's a brand new femzer requirement that came out middle of 2017 related to what they call team training. And the idea of being able to get all of the people in the same room, your IT guys, your skated guys, your pipeline controllers, your field technicians, your measurement guys and put them all into that environment and what that could mean for the industry in terms of what we could do with training. It could materially change really the quality of what we do because I mean the biggest challenge in pipeline operations is training in adverse or emergency operations. A lot of that's done even today as tabletop exercises and tabletop exercises are great, but they are limited in terms of what they can do in terms of physically creating the experience of the problem.

Yeah, that's one of the use cases that we actually even focusing on is enhancing tabletop exercises. So, you know, we're working on building that where and not only can we replicate like we have CAD drawings, we can replicate customer processes and entire plants, but we're also having a quote, level builder. So basically customers can just drag and drop and build their own processes themselves. So anyway, sorry, not trying to plug the product there.

And we've got a way before we go before we have a viable product. But yeah, hopefully, you know, what started out as a hobby is able to do something to help change and enhance the industry. All of technology is starts with somebody having an idea. So, you know, I really appreciate you sharing kind of the background of how you got the idea and how far you've come.

I know you have spent a lot of effort and a lot of time getting as far as you have come. And I'm really looking forward to see the product get to the market and you have a great deal of success with it. So, appreciate it. Well, look, we're kind of running a little longer than than than our typical episode, but man, it's great stuff.

I sure appreciate you joining us. And gonna be here. If somebody had questions about cybersecurity and some of the things you're doing, what would be the best way for them to get in touch with you? And you know what, I will do two things I will I will provide my email address as well as my my cell phone number, because I'm available for people to help someone I can help someone and I'm here my cell phone number is country code one here in the United States, and it's 281-832-3129.

It's my cell phone number and my email address is ClintCLANT. In my last name, Bo Dungeon, B-O-D-U-N-G-N at leosibersecurity.com. Okay, well, great. So, I know like with a lot of the episodes for the listeners, there's a lot of buzzwords and jargon.

And if you're not familiar with cybersecurity, you may not know a lot of what Clint was talking about. I know I have some homework to look some of that stuff up, but all of that will get captured on the podcast site for the episode. There will be show notes. There'll be a whole library of links there for if you want to take some time and kind of explore some of these ideas and learn more about some of the things that have been talked about.

Also, on the website, we'll have Clint's LinkedIn profile linked up so you can find him that way as well. So, thank you for listening and look forward to having you back next time. Thanks for the opportunity. It was fun being here.

So, one of the key things I like to do is try to summarize the whole conversation down to some simple takeaways that any of us could use to be better at doing our job as a pipeline. So, I take away several. One is the idea of a risk-based approach to cybersecurity. And that's simply stated is I understand what Clint was talking to us about is to look at the real risk related to cybersecurity and build your program related to that real risk.

Number two, when looking at how you're going to do that, when you do your risk assessment and you do your threat analysis, look at the data that you're going to monitor and make sure that that data is tied to what you're doing after the fact so that your ongoing risk assessment can be done in real time. And then, lastly, I think probably my biggest takeaway in this is that this issue of cybersecurity, there's a lot here. It's complex like a lot of other kinds of technology, but probably more than anything else. It's fast moving and really to do a good job of managing the risk.

You need resources that kind of live and breathe every day this content. So, that's our three takeaways for this episode. I hope you enjoyed this week's episode with the Pipeliners Podcast. I really enjoyed the conversation with Clint, Mo Dungeon, our guest, and I'm hoping he's going to come back as he releases his new books and finishes some of these cool tools he's working on.

Just a reminder before you go, you should register to win our customized Pipeliners podcast Yeti Tumblr. Simply visit pipelinerspodcast.com slash win. That's pipelinerspodcast.com slash win to enter yourself in the drawing. Thanks again for listening.

Talk to you next week.

Frequently asked questions

How long is this episode of Pipeliners Podcast?

This episode is 36 minutes long.

When was this Pipeliners Podcast episode published?

This episode was published on December 19, 2017.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this Pipeliners Podcast episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.