Latest / Onapsis Podcast / Fireside Chat: Security and Compliance in the Shared Responsibility Model with OG&E and Onapsis

Transcript

Fireside Chat: Security and Compliance in the Shared Responsibility Model with OG&E and Onapsis · Onapsis Podcast

• 0:11
  Speaker 2: And thanks for joining us today and welcome to Fireside Chat, Security & Compliance in the Shared Responsibility Model with OG&E and Anapsis.
• 0:21
  Speaker 2: I'm Heather Alima, I am a content producer here at ASUG.
• 0:24
  Speaker 2: Today's webcast will be recorded.
• 0:26
  Speaker 2: you'll receive post-event email link on demand recording.
• 0:30
  Speaker 2: Please feel free to pass that link along to any colleagues if they found information useful.
• 0:36
  Speaker 2: And at the end of the webcast, a two-question survey is going to pop up on your screen.
• 0:41
  Speaker 2: Please take a moment to fill it out because we like to know what you think here at ASUG.
• 0:45
  Speaker 2: If you have any questions please enter them in the Q&A box over to your left and Any Questions We Don't Get To On The Webcasts?
• 0:52
  Speaker 2: We will be sure to answer offline.
• 0:55
  Speaker 2: Now I'll hand it off.
• 0:56
  Speaker 2: Paul Klein Schnitz CRO of Anapsis.
• 1:03
  Speaker 1: Heather, thank you so much for the introduction.
• 1:05
  Speaker 1: Thank you ASUG for hosting us.
• 1:07
  Speaker 1: I'm very excited for our Our conversation here today with my friend Ian Anderson from OG&E.
• 1:16
  Speaker 1: We'd love to start with some introductions So if i can get these slides to work.
• 1:32
  Speaker 1: All right Ian we're going to start With You!
• 1:33
  Speaker 1: I'd Love For You To Introduce Yourself As Well as your Company.
• 1:38
  Speaker 0: Well, good morning.
• 1:39
  Speaker 0: Good afternoon kind of wherever you are in the world.
• 1:42
  Speaker 0: My name is Ian Anderson.
• 1:43
  Speaker 0: I'm the director of enterprise security network and monitoring at Oklahoma gas and electric OGE.
• 1:49
  Speaker 0: We are a vertically integrated investor owned electric utility And that's all just kind of fancy talk for Where we're your electric company?
• 1:59
  Speaker 0: We transmit, we distribute electricity.
• 2:02
  Speaker 0: Ultimately we rub things together and get them to your house.
• 2:04
  Speaker 0: that's the electricity you use for power of businesses or lives.
• 2:10
  Speaker 0: everything in between.
• 2:12
  Speaker 0: so were headquartered in Oklahoma City, Oklahoma where we proudly serve a little over nine hundred thousand customers across the Oklahoma service area even into parts of Arkansas.
• 2:24
  Speaker 0: So for me personally, director.
• 2:28
  Speaker 0: I'm the executive responsible for all security cyber physical IT OT.
• 2:33
  Speaker 0: my teams also include our network and telecommunications team as well as are monitoring or observability team.
• 2:39
  Speaker 0: so been doing this SAP Security thing about close to ten years now.
• 2:46
  Speaker 0: It's been quite a lot has changed over the past decade.
• 2:49
  Speaker 0: So it's a real treat to get to come, you know?
• 2:51
  Speaker 0: To this group and hang out with UPK and talk about some of things that are going
• 2:56
  Speaker 1: on.
• 2:59
  Speaker 1: Thanks, Dianne.
• 3:00
  Speaker 1: Yeah, Youth OG&E has been great customer but more importantly partner of ours.
• 3:05
  Speaker 1: we've had longstanding relationship.
• 3:07
  Speaker 1: We appreciate the insights You provide us both from industry as well as features we put into product based your background.
• 3:16
  Speaker 1: So as mentioned earlier, I am Paul Kleinstance.
• 3:18
  Speaker 1: I'm our Chief Revenue Officer here at Onopsis, essentially I'm responsible for all of our customer-facing functions and onopsis.
• 3:27
  Speaker 1: we've been around for a while.
• 3:29
  Speaker 1: you know We have about over three hundred global two thousand customers.
• 3:35
  Speaker 1: One the things that were very proud is that we identified over one thousand zero day vulnerabilities.
• 3:40
  Speaker 1: in fact any given month we've identified forty to sixty percent of the vulnerability that SAP is ultimately generated patches for.
• 3:49
  Speaker 1: We're also, the only SAP endorsed security product within the portfolio.
• 3:56
  Speaker 1: what this simply means as you go through an annual certification both from a product perspective and shared resources across SAP and onopsis that are working together as we build solutions to help defend the likes of Ian, and Ogini in others.
• 4:15
  Speaker 1: And then lastly were very proud there our customer seesat is ninety six percent plus.
• 4:20
  Speaker 1: so with that let's jump into the content.
• 4:23
  Speaker 1: The format We're going use today has a fireside chat.
• 4:25
  Speaker 1: you know I just thought That You Know Going Through A Conversation Rather Than Much As Slides Would Be Of More Value and be more interesting To Everyone.
• 4:32
  Speaker 1: Yeah and Really?
• 4:33
  Speaker 1: We want to start With.
• 4:35
  Speaker 1: The topic of today, as mentioned is the shared responsibility.
• 4:40
  Speaker 1: It's a bit of a reality check for individuals especially As it relates to thinking about moving to rise.
• 4:45
  Speaker 1: You know the industry joke Is that shared responsibility often turns into shared blame when disability gaps are ignored.
• 4:53
  Speaker 1: When individuals like Ian and his organization look at moving to Rise The reality is SAPs in a phenomenal job And putting together the appropriate security controls and technologies to support the infrastructure in the cloud, but your data is still on.
• 5:09
  Speaker 1: And you're ultimately accountable for it?
• 5:11
  Speaker 1: Yeah.
• 5:11
  Speaker 1: Um then there's this intersection between security networking monitoring um Ian not just a security guy he sits right in the middle at OG&E between operations compliance security networking uh and monitoring where his central tip two understanding of problem solving further problems mitigating this.
• 5:36
  Speaker 1: So Ian, how about we jump in?
• 5:38
  Speaker 0: Yeah!
• 5:40
  Speaker 1: This first part is... We want to talk about who does what as it relates to the shared responsibility model.
• 5:46
  Speaker 1: yeah and The First question I have for you Is when You started this engagement And you looked at their rise contract What was the biggest ha-ha When It related To your responsibilities Versus S&P's Responsibilities and Ultimately Accountability?
• 6:01
  Speaker 0: Yeah i mean you know i think they're Properly answer that Question.
• 6:05
  Speaker 0: you got to go back like way before rise, right?
• 6:09
  Speaker 0: So our journey around SAP security really started in earnest around twenty seventeen.
• 6:16
  Speaker 0: Where we started kind of see the wind shift with things like ERPs and SAP specifically as a threat for organization.
• 6:27
  Speaker 0: I think lot us sit.
• 6:30
  Speaker 0: You worry about the email, you worry active director.
• 6:34
  Speaker 0: Like just have these systems that you worry more because we see it in news more or... And don't really think like an ERP your core business application what happens truly if an adversary gets a hold of that?
• 6:51
  Speaker 0: But as seen over past decade cyber criminals really focusing more on monetization rather than other impacts and denials.
• 7:02
  Speaker 0: SAP is ripe for that type of activity, so thats kinda what started us down this journey ten years ago with ECC.
• 7:11
  Speaker 0: you know, like many companies we had this very traditional SAP deployment is all on print.
• 7:17
  Speaker 0: It's kind of tucked away it's hidden.
• 7:20
  Speaker 0: by no means does that mean?
• 7:22
  Speaker 0: Was impervious right but there are different layers of abstraction.
• 7:27
  Speaker 0: the attacker has to do a whole lot more work in order.
• 7:31
  Speaker 0: But it was a real eye-opener because we recognize things like, hey our patching and note processes aren't necessarily conducive to the way modern world is shifting.
• 7:44
  Speaker 0: You see zero day go from your report down into concept of an exploitable package within days now rather than months.
• 7:53
  Speaker 0: And even for something as complicated as SAP We're seeing time to action shrink.
• 8:01
  Speaker 0: So when we first kind of got a hold on this contract and SIP is pitching the idea shared responsibility, great.
• 8:14
  Speaker 0: We like that because there's a lot... When you hear shared responsibilities really think partnership Right?
• 8:20
  Speaker 0: And so we went in with all these kind of preconceptions like, hey here's the stuff.
• 8:23
  Speaker 0: Like you're going to handle this and We're gonna handle that but we're gonna share some visibility because That's what partners do like.
• 8:29
  Speaker 0: we hold each other accountable.
• 8:30
  Speaker 0: We support each Other and it wasn't necessarily that right.
• 8:34
  Speaker 0: It was...we handled The infrastructure.
• 8:38
  Speaker 0: You don't worry about any Of which is a major, it was a major change for us.
• 8:42
  Speaker 0: Like when you own everything on Prim and you can really put your hands on the metal or devices You could go look at all of traffic that you want like there's nothing.
• 8:50
  Speaker 0: that kind gets in your way Of getting a holistic view Your environment.
• 8:56
  Speaker 0: And I think That has actually been probably more challenging shift For most companies.
• 9:03
  Speaker 0: They've gone from very IT centric ability to monitor and having a shift into this new paradigm, which is what shared responsibility calls for.
• 9:10
  Speaker 0: Which as an application centric monitoring in security program like you know.
• 9:17
  Speaker 0: so I'd liken SAP a lot to OT operational technology.
• 9:23
  Speaker 0: i call it OT of the business right?
• 9:25
  Speaker 0: So we're an electric company.
• 9:27
  Speaker 0: We've got power plants parts and things that are going on in our environment because we're producing this physical product, getting it out into the world.
• 9:41
  Speaker 0: When you look at the challenges we have on the OT side right?
• 9:45
  Speaker 0: You know these systems.
• 9:46
  Speaker 0: they get put in...and may live there for ten-twenty years!
• 9:51
  Speaker 0: Really only people who knows how those work or maybe folks just hung around.
• 9:57
  Speaker 0: so they've got decades of experience taking care some of their systems.
• 10:02
  Speaker 0: They don't handle change very well But for the most part, they're pretty reliable.
• 10:08
  Speaker 0: And then from a talent perspective it's kind of an niche area like finding someone that is really good with OT or OT security is really difficult.
• 10:17
  Speaker 0: Now if I hadn't used the words OT at all in my little statement there It would sound a lot like SAP as well.
• 10:24
  Speaker 0: We put in these SAP systems and they'll sit there for ten, twenty years.
• 10:27
  Speaker 0: And then we're like kind of forced upgrade.
• 10:29
  Speaker 0: SAP is really built on the backbone of people that have just done it forever!
• 10:34
  Speaker 0: Then if you want to get some talent either grow yourself or its expensive because theres not a ton of people out here.
• 10:42
  Speaker 0: so thats still legacy.
• 10:43
  Speaker 0: but now SAP are shifting all through shared responsibility model.
• 10:48
  Speaker 0: We kind of joke, we don't really view it as the shared responsibility model because what they're not sharing is accountability.
• 10:57
  Speaker 0: Because no matter what happens like oh you know their infrastructure gets popped our infrastructure gets pop but there's going to be finger point and there's the blame game all that stuff.
• 11:06
  Speaker 0: my customer is not going
• 11:08
  Speaker 2: to care.
• 11:09
  Speaker 0: My regulators are NOT GOING TO CARE.
• 11:11
  Speaker 0: They're gonna say well OGNEE THAT'S ON YOU.
• 11:13
  Speaker 0: And so regardless of Shared Responsibility it is not shared accountability.
• 11:18
  Speaker 0: That's one of the things that we can't as defenders and leaders, we cannot lose sight
• 11:24
  Speaker 0: off.".
• 11:27
  Speaker 0: We went in really excited where he was like oh well look its all Azure.
• 11:32
  Speaker 0: so just set up a log forwarding to see what are going on with infrastructure?
• 11:37
  Speaker 0: No!
• 11:38
  Speaker 0: Thats not what Shared Responsibility means
• 11:41
  Speaker 0: right?!
• 11:42
  Speaker 0: We were advocating for shared accountability responsibility.
• 11:46
  Speaker 0: And so that was kind of been the wake up and we realized like, hey... So now we have to really manage.
• 11:52
  Speaker 0: what are our true exposures?
• 11:53
  Speaker 0: What other things do you need a focus
• 11:55
  Speaker 0: on?".
• 11:56
  Speaker 0: It's at the app level!
• 12:00
  Speaker 1: I've heard others in similar roles as yours describe SAP more akin to OT or even referred to as shadow IT especially thinking about this idea that's not shared, no it is going to change.
• 12:17
  Speaker 1: Were there anything internal to your organization?
• 12:20
  Speaker 1: you had to do either educate or rally the appropriate stakeholders who drive awareness and acknowledge reality?
• 12:29
  Speaker 0: Yes certainly at first this was completely absent of rise but I literally have a security vendor.
• 12:36
  Speaker 0: ask me why so much about SAP Security?
• 12:40
  Speaker 0: And this is actually when we were trying to acquire onapsis for the first time.
• 12:43
  Speaker 0: A reseller told me that, too my face and it's like well then you clearly don't understand SAP or if you don't have some of these massive systems internally.
• 12:55
  Speaker 0: again speaking of the fragility or the perceived fragility of SAP in I think some of our legacy systems where probably in this condition there was real fear into SAP that it's going to harm performance.
• 13:09
  Speaker 0: It's going impact customers, its gonna impact financials and do all these things well.
• 13:14
  Speaker 0: luckily we had spent years kind of getting better in the OT security space so actually applied a lot those same concepts right?
• 13:22
  Speaker 0: So everything is passive.
• 13:23
  Speaker 0: you know the security tool like kinda fails for lack of a better phrase.
• 13:27
  Speaker 0: before the actual production tool uptime is paramount.
• 13:33
  Speaker 0: I got to tell you, the amount of stress testing that we put onto our onapsis products prior to allowing anything into production... We ended up shaking out more performance and supportability errors in other third-party tools than what business critical far more than anything on apps is found.
• 13:59
  Speaker 0: So like we were stress testing the,
• 14:01
  Speaker 2: The heck out
• 14:02
  Speaker 0: of our environment and finding it's all the other stuff that was causing problems but we're glad to know about It.
• 14:08
  Speaker 0: so That created an opportunity for us To tell that story.
• 14:11
  Speaker 0: Hey this Is not About Like security as a partner And security isn't integrated concept Of This We can help um...and we are Not here to bring you down.
• 14:23
  Speaker 0: That established a little bit of the rapport.
• 14:25
  Speaker 0: So going into rise and that migration, it made a lot more sense.
• 14:29
  Speaker 0: And we could even say things like hey... We're doing code analysis.
• 14:34
  Speaker 0: so let's not inject bad code.
• 14:36
  Speaker 0: because when I went back to look at all our old legacy codes in ECC some of those are very good.
• 14:44
  Speaker 0: People here attending may be shocked oh my god there is bad ABAP out there?
• 14:50
  Speaker 0: Yeah!
• 14:53
  Speaker 0: So, we were able to say like hey let's try and get clean.
• 14:58
  Speaker 0: And stay clean.
• 15:00
  Speaker 0: throughout this deployment We used it as a tool to kind of tell a positive story about how...we are very intentional around the supportability The security and maintain ability in our SAP environment.
• 15:16
  Speaker 0: One thing that has helped out huge is you know, SAP vulnerabilities are starting to become more common.
• 15:23
  Speaker 0: And so like onapsis threat intelligence actually will send something out and be able to go into the platform.
• 15:30
  Speaker 0: So let me just tell a story.
• 15:34
  Speaker 0: I think it was like The Wall Street Journal or MSN or something published your story about how SAP environments were getting hacked and it caused almost like this little panic among the, you know in a C-suite they will read that be like oh we also use SAP.
• 15:48
  Speaker 0: Like how in trouble are we?
• 15:50
  Speaker 0: Are we the next
• 15:50
  Speaker 0: Jaguar?".
• 15:52
  Speaker 0: And then you can go into to um you know into the platform and you can see.
• 15:57
  Speaker 0: yep!
• 15:58
  Speaker 0: We see the vulnerability hear the devices.
• 16:04
  Speaker 0: Either we validated that were not susceptible or have a direct path to know what is susceptible.
• 16:10
  Speaker 0: And just being able speak at level of intentionality and control over your own environment on the side, it's incredibly powerful!
• 16:21
  Speaker 0: We've been sure tell right stories build relationships which has made the rise transition easier from security because we're not creating these relationships on the fly.
• 16:38
  Speaker 0: We've established this rigor and this rapport, now we are leveraging tools to drive projects forward.
• 16:45
  Speaker 1: It sounds like being able respond to scenarios that's responding to news articles or anything else within board level executive levels even in your teams tries another level of confidence with an organization?
• 17:00
  Speaker 0: At end-of-the-day what were trying do is make right tooling process decisions, we're trying to develop the right people.
• 17:07
  Speaker 0: So one when bad happens because it's going to happen where ready today that were ready to handle it but also like you know what?
• 17:13
  Speaker 0: We are thinking strategically like the net.
• 17:15
  Speaker 0: next ask the next need is coming and so look at your art our belief as if or efficient for effective-if we are doing things intelligently its a lot easier.
• 17:26
  Speaker 0: So let's
• 17:37
  Speaker 1: transition to compliance for a second.
• 17:41
  Speaker 1: We all know that compliance is meant be in place to help security and the mechanism of control.
• 17:47
  Speaker 1: Utilities are obviously under our microscope, whether it's NERC-CIP or other regulations.
• 17:52
  Speaker 1: how did they move to rise?
• 17:53
  Speaker 1: either simplify or complicate
• 17:55
  Speaker 0: them?
• 17:59
  Speaker 0: Wow!
• 18:00
  Speaker 0: That's good question from a federal regulatory perspective.
• 18:07
  Speaker 0: if you're an electric utility You know, the big challenge is around NERC-SIP.
• 18:14
  Speaker 0: We've kind of like bifurcated or separated ourselves from that to reduce our
• 18:19
  Speaker 2: compliance
• 18:19
  Speaker 0: related exposure.
• 18:20
  Speaker 0: but it's interesting.
• 18:22
  Speaker 0: SOX, Sarbanes Oxley is absolutely still in play.
• 18:25
  Speaker 0: so if you're publicly traded and have to align with that honestly we took as an opportunity actually get better.
• 18:37
  Speaker 0: We went and reviewed our processes, redefined them.
• 18:39
  Speaker 0: And then we built in the controls that were necessary from an app's platform perspective... There is a little bit of feedback.
• 18:50
  Speaker 0: I don't know if it was me?
• 18:52
  Speaker 0: I hope not.
• 18:54
  Speaker 0: So
• 18:54
  Speaker 1: anyway.
• 19:00
  Speaker 0: so we took as opportunity to kind of redefine some of our compliance processes.
• 19:09
  Speaker 0: um having this concept of like the tools work for us rather than we worked for the tools because what we saw over the past like twenty years uh living with ecc was that a lot of our processes started to kind of take on a tent of, well were there to
• 19:24
  Speaker 2: feed
• 19:24
  Speaker 0: the beast that is ECC working actively for us.
• 19:29
  Speaker 0: And so as we kind of redefine, and then figuring out what are the right integration points?
• 19:35
  Speaker 0: One of the real challenges we've had around just being able to do investigative things when it comes to compliance level activity.
• 19:42
  Speaker 0: So in that's one thing that we'd been really proud to get to work with you all on the investigate solution or module.
• 19:54
  Speaker 0: So we can say, hey, we still have this type of activity.
• 19:57
  Speaker 0: Where else can we find this?
• 19:59
  Speaker 0: And it's almost like were able to now do threat hunting but from a compliance perspective.
• 20:05
  Speaker 0: Now compliance you'll hear me readily argue compliance does not equal security But they can't work together.
• 20:11
  Speaker 0: and so if we're able to say got the secure environment obviously some sort of control needs to be tuned or adjusted, and how do we go do that?
• 20:21
  Speaker 0: To ensure that were meeting the compliance related need.
• 20:27
  Speaker 0: That's been pretty successful.
• 20:29
  Speaker 0: so you gotta take this like migration or whatever your doing.
• 20:31
  Speaker 0: if you're moving into RISE You have to take it as an opportunity rather than a punishment.
• 20:37
  Speaker 0: Go change things for better because not gonna get another chance once thats in its end None of us can go change our legacy ECC environments.
• 20:47
  Speaker 0: So why do we think that?
• 20:48
  Speaker 0: We're going to be able to put stuff in and then go clean up.
• 20:50
  Speaker 0: And Put security in after the fact.
• 20:52
  Speaker 0: it's not, It's just not gonna work very
• 20:53
  Speaker 1: well.
• 20:55
  Speaker 1: you know what I mean.
• 20:55
  Speaker 1: That's so true an um.
• 20:57
  Speaker 1: i've heard You mentioned a couple times whether its on this webcast or Just conversations you and I have had which is Um you can't defend What you don't see.
• 21:06
  Speaker 0: that's right um.
• 21:07
  Speaker 1: and so how Do you gain The visibility into an environment that your Not physically managing?
• 21:12
  Speaker 0: Well yeah What a hassle, because we have traditionally relied upon network level controls like the ability to just see at a packet-level who's coming and going.
• 21:29
  Speaker 0: We've had really adjust and embrace some of the new world order.
• 21:34
  Speaker 0: so one other thing is that I probably think about this too much this concept called cyber persistence theory.
• 21:42
  Speaker 0: So just for everyone's awareness, my side hustle I'm on the faculty at Arizona State University and I teach in the Master of Arts in Global Security program.
• 21:50
  Speaker 0: so if you're looking for a good masters You should check that one out.
• 21:55
  Speaker 0: but what are classes?
• 21:55
  Speaker 0: I teaches around cybersecurity strategy planning And we really starting to focus on this concept of cyber persistence Theory which basically says that look This idea that we are deterring negative cyber activity is crazy.
• 22:11
  Speaker 0: It's just not the reality, and what they're saying?
• 22:14
  Speaker 0: that you know this Cyber domain itself.
• 22:16
  Speaker 0: it like this domain of persistent contact which in interesting take when apply to rise.
• 22:22
  Speaker 0: because look Rise Is now putting yourself out into some sort of hyperscaler.
• 22:28
  Speaker 0: You can either be directly exposed to internet partially exposed fully encapsulated but are in a different kind of touch area, right?
• 22:39
  Speaker 0: You can't hide behind obscure IP addresses.
• 22:44
  Speaker 0: The friction is very, very different.
• 22:46
  Speaker 0: for an adversary to come touch you which is what the cyber persistence theory calls forth says like in traditional battle spaces like Kinetic and all that...you actually have to cross an ocean or get somewhere.
• 23:00
  Speaker 0: well really For something like SAP rise environment anyone in world could touch it.
• 23:05
  Speaker 0: It's as much a feature, it is a bug.
• 23:08
  Speaker 0: Now so what we're trying to do... We are trying to reduce down the opportunities for exploitation in areas that we can't control and so exploitation occurs through traditional SAP approach of things which is role-based access control.
• 23:28
  Speaker 0: You handle that.
• 23:29
  Speaker 0: So authentication authorization, but beyond that like exploitation still occurs at a code level and that's still where the vast majority folks are weak.
• 23:40
  Speaker 0: And so that's where like on apps is coming in saying hey we've got you know On the application layer The layer that we can control We have the appropriate vulnerability response Where seen things going in or monitoring for you know, types of activity that are indicative of exploitation.
• 24:00
  Speaker 0: because that's where we're kind of forced to go have that battle
• 24:04
  Speaker 1: on.
• 24:08
  Speaker 1: Our abstract mentions early decision or making decisions really in the process as moving into any type of hyperscaler is critical.
• 24:20
  Speaker 1: Yeah You could go back and based on lessons learned the decisions you made that were key early.
• 24:28
  Speaker 1: What would be a couple, whether technical or procedural guardrails to put in place?
• 24:33
  Speaker 1: Or do you recommend individuals are looking at this putting placed now or earlier?
• 24:38
  Speaker 0: Yeah it's weird deal because SAP is also moving so fast and things are changing continuously.
• 24:49
  Speaker 0: And so whatever you put in, You need to really understand and be flexible.
• 24:55
  Speaker 0: So as an example there's a lot of ask around like clean core right?
• 25:00
  Speaker 0: Oh we want to go to the clean core Right.
• 25:02
  Speaker 0: what that is not saying?
• 25:04
  Speaker 0: Like?
• 25:05
  Speaker 0: I think That There's some confusion Of there's clean core Then there's custom code right.
• 25:10
  Speaker 0: Clean Core Is Not Calling for The Elimination of Custom Code Right.
• 25:14
  Speaker 0: And so custom code is getting pushed into.
• 25:15
  Speaker 0: this thing called BTP, which frankly Is a new paradigm for SAP?
• 25:22
  Speaker 0: It's kind of a new product and we already like Paul or PK We ran in to issues between Ogenio Napsis Like how are we even you know How does BTP license if we had To go work through that?
• 25:34
  Speaker 0: because I looked at the ground was shifting under both Of us and what were realizing Was micro segmenting A lot of our BTP areas.
• 25:43
  Speaker 0: But that wasn't necessarily conducive to licensing and it created identity access management challenges, things like that.
• 25:49
  Speaker 0: So what I would recommend is whatever you do build in flexibility because the thing will change around you... It's my personal opinion.
• 26:01
  Speaker 0: a lot of rise has been designed for building an airplane as we fly Right, and we went live about a year ago.
• 26:09
  Speaker 0: And I can tell you like structurally A lot of things have already changed.
• 26:12
  Speaker 0: now It's kind of smoothing out a little bit for us.
• 26:14
  Speaker 0: You know these deployments are so big and complicated but it is important that you have an organization That can pivot in make some adjustments because the cloud Is going to require that.
• 26:29
  Speaker 0: Now let's go make lemonade out of lemons Because that sounds terrible But once your start better at like being able to move quickly.
• 26:38
  Speaker 0: There's other benefits that come with that, so going back the cyber persistence theory and let's just talk about vulnerabilities.
• 26:45
  Speaker 0: So the average time of a vulnerability you know?
• 26:48
  Speaker 0: To go from like hey zero day announcement or patch notification Or so an in-day if you will You know was for SAP could have been like thirty days or something.
• 26:57
  Speaker 0: I mean it's gonna get boiled down to literally a day.
• 27:00
  Speaker 0: It'll eventually maybe get boiled on two hours thanks artificial intelligence Right?
• 27:05
  Speaker 0: So now as organizations, we have to be able to patch faster.
• 27:11
  Speaker 0: We have to move quicker because our exposure to the adversary is different now and can't hide behind a lot of traditional controls that we've relied upon in the past.
• 27:23
  Speaker 0: so go remove opportunities for exploitation rather than create the wall, right?
• 27:30
  Speaker 0: Like there is no big firewall that's coming to save you.
• 27:33
  Speaker 0: We have to go actually make institutional fixes at the code level or the process level of a system level in order to reduce opportunities for
• 27:42
  Speaker 0: exploitation.".
• 27:44
  Speaker 0: So like... That's where I see the big challenge for us organizationally not just at OG&E.
• 27:50
  Speaker 0: we're getting better but i think across the entire landscape as were collection of users used to patching maybe monthly.
• 28:01
  Speaker 0: I know, i've seen some shops that have patched twice a year.
• 28:04
  Speaker 0: you now there's an HR patch and then the daylight savings patch or whatever.
• 28:07
  Speaker 0: right.
• 28:08
  Speaker 0: so theres like two of these patches.
• 28:10
  Speaker 0: they throw all notes in its just this big endeavor.
• 28:12
  Speaker 0: we're gonna get leaner were going to be faster because thats what the adversary is going force our hand into.
• 28:22
  Speaker 1: You know your insights on those subjects are always fascinating.
• 28:30
  Speaker 1: What I'd like to really transition into is, what's next for Ogini?
• 28:35
  Speaker 1: Maybe touch on.
• 28:36
  Speaker 1: you mentioned earlier the new product that Anopsis has launched called Investigate.
• 28:42
  Speaker 1: Yeah would love for the audience learn how was your relationship with us evolve?
• 28:47
  Speaker 1: What are you expecting from us in general?
• 28:50
  Speaker 1: and maybe How were you planning using this investigate project?
• 28:53
  Speaker 0: yeah so We like a lot of companies out there.
• 28:58
  Speaker 0: I think that we really value being able to control our own destiny at some level, right?
• 29:03
  Speaker 0: So um i don't like the play victim...I'd like to call the shots and so you know what we're trying to do is kind of gain initiative over your environment.
• 29:16
  Speaker 0: What does this mean?
• 29:18
  Speaker 0: for most us it's just a fancy way.
• 29:20
  Speaker 0: The problem is we don't really know how to hunt in some of these environments.
• 29:25
  Speaker 0: And even with the hunt, what do we do about it?
• 29:29
  Speaker 0: So you know, what we're going to be looking to do is like How are we intaking threat intelligence and not just indicators or compromise right where We were moving so far beyond?
• 29:38
  Speaker 0: Just like oh, you know IP's hashes Like that's table stakes.
• 29:42
  Speaker 0: If if You're Not doing That Today like Your Really Going To Have Some Significant Challenges What Were Looking At Is TTPs.
• 29:50
  Speaker 0: And because what we see is the advanced adversaries are living off of land, they're taking identities.
• 29:54
  Speaker 0: They're pivoting their exploiting internal there doing all sorts interesting stuff.
• 29:59
  Speaker 0: We don't necessarily know What that looks like in our own environment.
• 30:03
  Speaker 0: and so things like adversary emulation mixed with high end investigative capabilities That will help us hunt forward With a byproduct band.
• 30:13
  Speaker 0: now we go tune or security controls.
• 30:16
  Speaker 0: So, you know what we do at OG&E is We take in thread intel.
• 30:20
  Speaker 0: We emulate the activity and then we say all right Did my tools see it?
• 30:25
  Speaker 0: did they alert on It?
• 30:26
  Speaker 0: did They block it In that order because You can't block you can't alert when you don't See And you certainly Can't lock What you Don't see.
• 30:34
  Speaker 0: so we Do have That cascade.
• 30:36
  Speaker 0: also don't necessarily want to Block everything just offhand.
• 30:39
  Speaker 0: Right you Want To maybe Say like Is this worth blocking?
• 30:43
  Speaker 0: What are some of the downstream impacts?
• 30:45
  Speaker 0: And by the way, you learn this the hard way when you start messing around with OT systems.
• 30:50
  Speaker 0: It's not always the best idea to just kill a process.
• 30:53
  Speaker 0: This is not IT right and that's why I would argue like ERPs aren't IT they're very different.
• 30:59
  Speaker 0: I don't know if i can call them OT but their very different than your traditional IT services.
• 31:05
  Speaker 0: so what we will be working on?
• 31:07
  Speaker 0: how do want ensure getting value out out of our investments.
• 31:13
  Speaker 0: So like we're challenging them, We are seeing how they operate based upon actual threat intelligence and how the adversary is actually working.
• 31:21
  Speaker 0: then were tuning our controls And uh...and we're seeking to move faster Like that's.
• 31:27
  Speaker 0: That's The goal..And I think the rise environment actually lends itself To some Of those capabilities.
• 31:35
  Speaker 0: You know
• 31:36
  Speaker 1: Ian.
• 31:36
  Speaker 1: um I want to turn this over to Q&A here in a second but I love this quote from you where, and if you've touched on it actually several times in the discussion but security isn't a project phase.
• 31:48
  Speaker 1: It's a foundation.
• 31:49
  Speaker 1: yeah If you wait for security to-if you way for that phase of your Verizon regulation You have already lost.
• 31:54
  Speaker 1: Yeah Is there any additional parting kind of wisdom or recommendations?
• 31:58
  Speaker 1: Or even coaching for those who are On The Line Are listening?
• 32:06
  Speaker 0: There's so many now opportunities out there.
• 32:09
  Speaker 0: So look, we just deployed rise were already working on a big upgrade.
• 32:13
  Speaker 0: These things are coming back again.
• 32:15
  Speaker 0: it is never too late to get started and start building the relationships.
• 32:21
  Speaker 0: our initial entry into SAP security space was hard because introducing new concepts.
• 32:28
  Speaker 0: but like an ERP nothing will be done in repetition, it takes focus.
• 32:37
  Speaker 0: It takes intentionality.
• 32:38
  Speaker 0: showing up every single day we kind of joke about.
• 32:42
  Speaker 0: like a lot of the times my security team feels like you know were tourists right?
• 32:47
  Speaker 0: We show up looking around.
• 32:49
  Speaker 0: this is kinda neat.
• 32:50
  Speaker 0: your just learning and you're there to let tour guide tell ya all cool stuff that can do.
• 32:58
  Speaker 0: thats where its begins.
• 33:00
  Speaker 0: so don't be afraid being tourist probably with a lot And I know, I've kind of fought this at times.
• 33:08
  Speaker 0: It's like you go in and people look to you for answers or they looked.
• 33:11
  Speaker 0: he was like oh You're the smart guy in the room.
• 33:13
  Speaker 0: Go be the dumb guy in there.
• 33:15
  Speaker 0: Just go listen just go learn and then you come back and always Be offering something.
• 33:22
  Speaker 0: One other things PK can attest one thing that i'm Always pushing our vendors on is The days having these really expensive security specific tools are coming to an end because we're now approaching a point where leaders, so executive teams you know shareholders right like everyone is looking and saying okay I've got this tool like Onapsis.
• 33:48
  Speaker 0: And it sits in this wonderfully privileged part of a very important system.
• 33:54
  Speaker 0: what other value can i go derive out?
• 33:58
  Speaker 0: And so one of the things I've liked about working with PK and his team is, this how I think.
• 34:05
  Speaker 0: When I throw out ideas like hey what if it could do this?
• 34:09
  Speaker 0: The answer is huh!
• 34:11
  Speaker 0: It's not really what we do.
• 34:13
  Speaker 0: you know its always okay.
• 34:15
  Speaker 0: help us understand value because ultimately security has to continue being a value add in just the cost center.
• 34:22
  Speaker 0: We're already expensive enough
• 34:24
  Speaker 1: right
• 34:25
  Speaker 0: Once we add value because we sit in unique places and have unique perspectives on the things that are, interactions that are going on these systems.
• 34:32
  Speaker 0: It becomes way more valuable to the organization And that's how you become sticky.
• 34:37
  Speaker 0: How do get other teams using your security tools?
• 34:39
  Speaker 0: Not just the security team themselves.
• 34:42
  Speaker 1: You know it's Ian is one of the reasons why
• 34:44
  Speaker 0: our
• 34:45
  Speaker 1: organizations Have had such a strong and positive relationship.
• 34:49
  Speaker 1: Is We value this thing very similar things In fact whenever core values is hacking And really what that means is celebrating and encouraging individuals within our organization to experiment, try new things.
• 35:01
  Speaker 1: There's not a negative consequence for doing so in having feedback from customers like yourselves.
• 35:09
  Speaker 1: either we collectively hack it then maybe generate some feature or wind teller whatnot.
• 35:15
  Speaker 1: It actually testament the product launched as well.
• 35:19
  Speaker 1: We appreciate their relationship.
• 35:23
  Speaker 1: At this point, I'm going to turn this back to Heather.
• 35:25
  Speaker 1: To open up for Q&A
• 35:32
  Speaker 2: All right So if you have any questions please go ahead and enter them in that q&a box over to the left And we will get started.
• 35:40
  Speaker 2: guys it looks like you have a friend in here.
• 35:43
  Speaker 2: He says Ian Varela Forgive me If i mispronounce your name Says hi Ian and ball.
• 35:48
  Speaker 2: This is Ian varela from Cypher BSC.
• 35:52
  Speaker 2: How did OG&E balance SAP's portion of the shared responsibility model with your own accountability for the application layer?
• 36:05
  Speaker 0: Spam call.
• 36:06
  Speaker 0: Sorry, okay.
• 36:08
  Speaker 0: Hey Ivan great question.
• 36:10
  Speaker 0: So how do you need balanced SAPs portion Of this shared responsibility with our own accountability?
• 36:18
  Speaker 0: You know.
• 36:19
  Speaker 0: so We try to do some things around.
• 36:24
  Speaker 0: how are we creating opportunities for visibility in places that we do control, right?
• 36:30
  Speaker 0: So this idea of an ERP is one hundred percent isolated and its own environment.
• 36:43
  Speaker 0: pretty much anything.
• 36:44
  Speaker 0: So what we did is, we set up opportunities and detection points at those kind of gateways so we can at least see some things that are going on.
• 36:55
  Speaker 0: then you know?
• 36:55
  Speaker 0: We attempted to derive logs out the out of SAP.
• 37:01
  Speaker 0: That maybe indicates like hey!
• 37:03
  Speaker 0: We've got a long running batch job or these challenges These thing's Going On.
• 37:09
  Speaker 0: What You won't necessarily get from SAP Is that clear check mark guidance of like, yeah you do this.
• 37:16
  Speaker 0: This and this they basically just say.
• 37:18
  Speaker 0: anything beyond the infrastructure is your responsibility?
• 37:21
  Speaker 0: And so we had to kind of figure out how go get clever and hack it in a way.
• 37:27
  Speaker 0: all right given these connections giving data points what are some assumptions that could make about not only security the environment, but also the performance?
• 37:39
  Speaker 0: because performance matters.
• 37:41
  Speaker 0: That's what your customers are going to be looking at.
• 37:43
  Speaker 0: they security is expected.
• 37:45
  Speaker 0: you know performances expect it.
• 37:48
  Speaker 0: so how are you tracking risk mitigation efforts and performance cyber security KPIs?
• 37:55
  Speaker 0: across all of Genie.
• 37:57
  Speaker 0: we got some things with SAP specifically onapsis as our partner And So that does have some robust reports.
• 38:06
  Speaker 0: One of the things that has been great is some organizations will outsource elements in their SAP support stacks, like BASIS for example.
• 38:19
  Speaker 0: We always wonder how do we keep bases accountable?
• 38:22
  Speaker 0: Because really it's there job to do this stuff right and so And actually build in KPIs and things like that into these agreements, saying hey we're expecting this level of vulnerability management.
• 38:38
  Speaker 0: This time to act, you know?
• 38:40
  Speaker 0: This amount of time to kind get these notes in, these fixes then reduce risk.
• 38:46
  Speaker 0: So the platform has been a great tool Good question.
• 38:51
  Speaker 0: Thank You
• 38:53
  Speaker 2: Thanks for your answer.
• 38:55
  Speaker 2: So the next question is we have some systems on rise, not ERP.
• 39:00
  Speaker 2: Rise has lots of security holes inherent in the build for example enforcement of encrypted RFC which violate SIPA's own recommendations.
• 39:09
  Speaker 2: so how are you dealing with that?
• 39:11
  Speaker 0: Probably the same way you are Darrell I mean... We're doing our best because it is like.
• 39:16
  Speaker 0: i mean It's a real interesting Interesting thing, right?
• 39:20
  Speaker 0: Because they've got some stuff that's like in rise.
• 39:23
  Speaker 0: But then they'd get a whole suite of other applications that are not so like success factors field class.
• 39:30
  Speaker 0: I mean don't even give me started on my IG and IS And some of the other.
• 39:35
  Speaker 0: you know three letter acronyms That are really four-letter words If you catch by drift We we You know.
• 39:44
  Speaker 0: one of things it's maddening to me is the lack of firefighter continuity across their their services, right?
• 39:50
  Speaker 0: So Firefighter is a critical control for many of us to go and manage admin rights.
• 39:58
  Speaker 0: It's almost like SAP pioneered in some ways with the GRC module Man, the Microsoft intro deployment of privileged identity management which is effectively just like in the firefighter process.
• 40:16
  Speaker 0: Is so much better than what SAP has and it's so much more consistent Which is crazy to talk about like microsoft having a consistent security strategy against their cloud properties.
• 40:27
  Speaker 0: So Like that's more The struggle that I've been experiencing not only in just like the gaps and coverage, I'm saying oh yeah you can't encrypt this or that but other tooling services we do rely on that are SAP owned and developed.
• 40:47
  Speaker 0: We're not seeing consistently deployed across their apps.
• 40:51
  Speaker 0: now part of it is they buy these products quickly integrating it because I got to get into market, but its like behind.
• 40:59
  Speaker 0: It doesn't follow some of the same access control mechanisms...I'll go back my earlier statement.
• 41:09
  Speaker 0: there's a lot building airplane while we fly and so this is where i say being nimble be an agile you know having organization that resilient going pay off big time as continue smooth these things out.
• 41:24
  Speaker 0: We all know SAP doesn't turn on the dime, so I would expect these conditions to persist for a bit.
• 41:33
  Speaker 2: Thank
• 41:34
  Speaker 0: you with the answer Darrell was looking for but it is what
• 41:39
  Speaker 2: It does not have to be.
• 41:40
  Speaker 2: just has been real
• 41:43
  Speaker 0: right?
• 41:43
  Speaker 0: Yeah So look i'm not shy too.
• 41:46
  Speaker 0: kind of bag on SAP where they deserve.
• 41:51
  Speaker 0: now I will say going back this shared responsibility model.
• 41:55
  Speaker 0: but there's so much potential value in SAP controlling the infrastructure.
• 42:00
  Speaker 0: There is so much financial value and just some of the micro segmentation, and just leveraging the cloud for how it has truly been designed like I think we initially even looked at what if we host our own SIP environment?
• 42:13
  Speaker 0: And all were going to do was really replicate what we're doing on physical data center up into the Cloud which is using the Clouds or all along reasons.
• 42:24
  Speaker 0: the immense amount of value in allowing SAP to manage the infrastructure and do things along those lines.
• 42:32
  Speaker 0: It does hurt my soul a little bit, not be able to see because I'm trust but verify guy?
• 42:38
  Speaker 0: See what's going
• 42:39
  Speaker 0: on?".
• 42:39
  Speaker 0: But I do believe that rise implementation is right direction.
• 42:43
  Speaker 0: we will get where we need it as us frontiersmen.
• 42:49
  Speaker 0: you know customers.
• 42:51
  Speaker 0: It's going to be interesting for a bit.
• 42:56
  Speaker 2: Well, thank you.
• 42:58
  Speaker 2: SAP pushes the clean core methodology heavily for rise customers.
• 43:04
  Speaker 2: We all know this.
• 43:06
  Speaker 2: Clean Core is hot topic.
• 43:07
  Speaker 2: So Ian how does having a specialized security partner like an absus help?
• 43:12
  Speaker 2: You maintain a clean core while ensuring your custom utility extensions don't introduce new vulnerabilities.
• 43:19
  Speaker 0: Yeah I. so i don't think it actually helps us.
• 43:22
  Speaker 0: Like I don't look at Fundamentally, I don't view it as a clean core versus unclean core.
• 43:28
  Speaker 0: I viewed this clean code versus UncleanCode.
• 43:32
  Speaker 0: The location of the code matters.
• 43:36
  Speaker 0: If you say clean core really does absolve SAP like other structural issues and things that they may have to deal with?
• 43:44
  Speaker 0: In their best interest for you not go mess-with the core code set into leverage PTP For many, many reasons.
• 43:54
  Speaker 0: But you know.
• 43:55
  Speaker 0: so for us where does O-Napsis fit in?
• 43:58
  Speaker 0: Well I mean it is literally just the code scanning piece.
• 44:02
  Speaker 0: but we underwent this challenge years ago were started really looking at quality of our Java and ABAP code because like a lot organizations you know, probably outsourced pieces of that development and we brought it in.
• 44:16
  Speaker 0: And yeah, We did the code review on everything.
• 44:17
  Speaker 0: but Did The Code Reviewers Know All The Nuance Of All The Different RFC Calls?
• 44:27
  Speaker 0: Right?
• 44:28
  Speaker 0: And so what SAP has allowed us to do, or excuse me.
• 44:30
  Speaker 0: What Onapsis have allowed is go and take that code and say all right are we aligning with kind of basic standards?
• 44:36
  Speaker 0: and where we're at now is were not introducing critical vulnerabilities because it gets stopped before that happens.
• 44:45
  Speaker 0: Onapsise has done a great job like getting into the DevSecOps pipeline and saying like, hey we're gonna prevent the bill.
• 44:51
  Speaker 0: We're going to prevent that migration until we get some clean
• 44:54
  Speaker 0: code.".
• 44:55
  Speaker 0: And it will take your developers off at first but ultimately ends up saving you a lot of headache from your parent pulling things back or your security team spending the weekend looking at a problem.
• 45:06
  Speaker 0: just let's develop cleaner code in also set an expectation where not just here to bang out some crummy code and just get into production so I can cash my check go home for today.
• 45:17
  Speaker 0: These are real implications.
• 45:19
  Speaker 0: So I don't want us as an industry to focus on clean core versus not or whatever, I think what we really need to do is focused on clean code.
• 45:28
  Speaker 0: What i also don't like though Is that can necessarily scan the code that SAP puts in?
• 45:35
  Speaker 0: Because i'm sure That has its problems too.
• 45:38
  Speaker 1: You know i'll jump in real quick especially since We're talking about clean code.
• 45:42
  Speaker 1: you Know one thing and then all mentioned.
• 45:44
  Speaker 1: so it's obvious our platform doesn't distinguish whether it's human generated or AI-generated code.
• 45:53
  Speaker 1: It provides the same level of value and a different level of identification vulnerabilities, so as all of us are trying to figure out what AI means in our worlds how we manage agents and likely code generated from those agents just I wanted make sure everyone is aware that our product does not distinguish.
• 46:13
  Speaker 1: It'll provide the same value and, you know go through it.
• 46:16
  Speaker 1: And identify the same vulnerabilities.
• 46:20
  Speaker 2: Absolutely Thank You Okay.
• 46:24
  Speaker 2: so next question is for utilities The audit cycle never really ends.
• 46:30
  Speaker 2: In a move to rise of this shared responsibility model Have found that your internal or external auditors had changed their approach?
• 46:38
  Speaker 2: How did prove them That the shared components were actually secure?
• 46:45
  Speaker 2: Yeah,
• 46:46
  Speaker 0: I mean they
• 46:49
  Speaker 1: oh my god.
• 46:49
  Speaker 1: We you
• 46:50
  Speaker 0: know we got beat up on that like the shared model because these are stock systems.
• 46:56
  Speaker 0: They want to know well what changes are happening?
• 46:58
  Speaker 0: What's going on?
• 46:59
  Speaker 0: and it's like yeah Well we don't really.
• 47:01
  Speaker 0: no were kind of blinded To It!
• 47:03
  Speaker 0: They Don't Want to call it a SASS.
• 47:04
  Speaker 0: they dont wanna Call it A PASS its SAP RISE Its own unique animal.
• 47:10
  Speaker 0: Where where we benefited is just.
• 47:14
  Speaker 0: We try not to be adversarial with our auditors, because one as this question rightfully calls out the cycle never ends.
• 47:21
  Speaker 0: And so these people are coming right back around seeing a lot of organizations kind of go more.
• 47:26
  Speaker 0: I'm going to be antagonistic toward my auditor and it never ends up well.
• 47:31
  Speaker 0: So what we really focus on is like all right how do we get to a shared okay?
• 47:35
  Speaker 0: Right Like i know i'm not gonna get everything right?
• 47:39
  Speaker 0: And so we try to have these relationships.
• 47:41
  Speaker 0: because then, we can leverage those relationships and say like hey here's the reality that we're dealing with.
• 47:46
  Speaker 0: This is an OG&E making this decision-this is SAP.
• 47:50
  Speaker 0: um...and look you know our auditors are uh..you know they're trying to figure all this stuff out too!
• 47:57
  Speaker 0: So maybe this is an opportunity as a customer that we can help grow our auditors.
• 48:02
  Speaker 0: We can say, hey here's how we view this problem and then they can take it back to their partners and stuff like that... And-and we can start building a more reasonable kind of compliance stack.
• 48:13
  Speaker 0: um the paradigms are shifting things are different and so what they're going to be letting you know relying on?
• 48:18
  Speaker 0: Here's how I've traditionally done it.
• 48:20
  Speaker 0: well That's no longer available.
• 48:21
  Speaker 0: So How do i go?
• 48:22
  Speaker 0: answer something similar?
• 48:24
  Speaker 0: This is where onapsis comes in for us.
• 48:26
  Speaker 0: So one of the questions we get, well who's got dialogue access?
• 48:30
  Speaker 0: What are these firefighter accounts up to?
• 48:32
  Speaker 0: Well we actually have custom alerts that are all set-up to notify when certain types of events happen and it triggers an incident.
• 48:39
  Speaker 0: you do all sorts of stuff but then at the end of day we hand that report over our auditors.
• 48:44
  Speaker 0: they're like okay this gives me warm and fuzzy.
• 48:48
  Speaker 0: We can test with them.
• 48:53
  Speaker 0: Look, tools at the end of day.
• 48:55
  Speaker 0: And in PK this is not to dump on onapsis but like every tool out there is going to fail you at some point.
• 49:03
  Speaker 0: that's why we at Ogini don't really look at it.
• 49:06
  Speaker 0: Like tools are opportunities To communicate.
• 49:11
  Speaker 0: They are relationship building opportunities.
• 49:13
  Speaker 0: We take onapsis and we say, this is how I'm measuring performance of my groups.
• 49:18
  Speaker 0: This is helping keep customer stuff secure but also telling a story about effective management across more organization.
• 49:26
  Speaker 0: Working with our auditors to help make sure that were compliant with our SOX controls in getting favorable judgment shared by the board or stock shareholders.
• 49:36
  Speaker 0: You know, the people.
• 49:40
  Speaker 0: The relationships are what's actually going to pull you out of the fire.
• 49:43
  Speaker 0: that tool itself is just a mechanism to build those relationships and help streamline it make your little bit more operationally efficient
• 49:50
  Speaker 1: when trying to accomplish couldn't agree more
• 49:56
  Speaker 2: great.
• 49:57
  Speaker 2: um yeah sorry pk most of these are for Ian.
• 50:05
  Speaker 0: he likes it like oh great
• 50:08
  Speaker 1: Man, so we almost didn't hear me talk.
• 50:11
  Speaker 1: Ian's a star!
• 50:14
  Speaker 2: Well since most utility companies have a security operation center that monitors the network can you explain why a traditional Security Operations Center might be blind to an SAP level breach?
• 50:28
  Speaker 2: and how has OG&E bridged that gap?
• 50:32
  Speaker 1: Yeah
• 50:35
  Speaker 0: I mean with RISE they're looking at the wrong stuff The way we have traditionally went and I think maybe this electric utility industry, it's like... We are a cyber physical company.
• 50:48
  Speaker 0: Like we have very physical assets that we deliver in physical good.
• 50:51
  Speaker 0: We had a service territory.
• 50:53
  Speaker 0: everything is kind of geospatial its physical nature.
• 50:56
  Speaker 0: so for us you can't necessarily touch the packet but you can conceive one.
• 51:01
  Speaker 0: But what we're really talking about with Rise is monitoring this amorphous SAP thing.
• 51:09
  Speaker 0: And if you are an SAP outsider, like a lot of us... You don't know all these SKUs or everything's weird three-letter acronym for stuff and there's different landscapes.
• 51:24
  Speaker 0: it's this weird language and we've never really, I think the vast majority of security teams have never understood how to speak that language.
• 51:32
  Speaker 0: The Onapsis platform for us has been like almost a translator right?
• 51:37
  Speaker 0: And so when you know as we were implementing Rise We Were Lucky Enough To Have A Onapsus Resident Engineer Kind Of Helping Us Build Out A Lot These Things.
• 51:48
  Speaker 0: So What She Actually Went Did was she would walk through like, hey we saw this event in onapsis.
• 51:56
  Speaker 0: And then work with our SOC team and say when you see this is what it actually means because we don't speak SAP.
• 52:05
  Speaker 0: so we needed almost a Sherpa to help us understand some of the basics.
• 52:12
  Speaker 0: your SOC teams are smart.
• 52:14
  Speaker 0: all they really need You know, give me a little bit of push.
• 52:18
  Speaker 0: I need a little guidance and then...I'm smart person so i can go figure some these things out.
• 52:23
  Speaker 0: The way SAP operates is just inherently different than the other stuff that our defenders are asked to secure.
• 52:29
  Speaker 0: So thats why we've been blind.
• 52:33
  Speaker 0: And especially traditionally it's We've been able to hide SAP behind things that do fit our traditional like paradigms for securing an environment.
• 52:43
  Speaker 0: So it's been behind a firewall and network, you know we had access to the UNIX Linux logs or whatever right infrastructure logs?
• 52:51
  Speaker 0: Uh...we never really have focus on application side itself.
• 52:58
  Speaker 2: Nice
• 53:02
  Speaker 0: I love idea of having
• 53:03
  Speaker 1: a Sherpa Thanks.
• 53:05
  Speaker 1: A marketing team might steal that from you,
• 53:07
  Speaker 0: yeah?
• 53:09
  Speaker 2: So in the rise environment SAP handles some patching but the customer handles others.
• 53:15
  Speaker 2: how do you manage timing and testing of security patches so they don't disrupt the critical utility operations or billing cycles?
• 53:23
  Speaker 0: You know I don't know like what we're trying to do on the security side.
• 53:26
  Speaker 0: Like i'm not dictating That.
• 53:28
  Speaker 0: What i'm dictating is The reality that the adversary's moving faster And thus our processes must be more efficient.
• 53:35
  Speaker 0: But at the end of a day, like security only gets to wield that hammer every so often where it's like thou shall patch this within twenty four hours.
• 53:42
  Speaker 0: And we have to be very careful with how you wheeled that right?
• 53:45
  Speaker 0: Because if you wheel too often You'll lose and then you will loose your group.
• 53:51
  Speaker 0: So what were more trying do is really better understand criticality Vulnerability enrichment.
• 54:00
  Speaker 0: So things like, you know, the Napsys Intel, CISA Kev.
• 54:04
  Speaker 0: You just other... Like how critical is this skew?
• 54:07
  Speaker 0: How critical is business application?
• 54:09
  Speaker 0: What it's network exposure?
• 54:12
  Speaker 0: Is this accessible via the internet or do have to be internal?
• 54:15
  Speaker 0: Or what does the makeup of this thing...?
• 54:18
  Speaker 0: Well we have start getting out that oh its a CVE-TEN.
• 54:22
  Speaker 0: so I've got drop everything and go fix it.
• 54:24
  Speaker 0: well no thats not necessarily case.
• 54:28
  Speaker 0: not all vulnerabilities are created equal across all organizations.
• 54:31
  Speaker 0: In fact, a concept we're working on here at OG&E is actually something that's pushed by CISA and Carnegie Mellon out of Pittsburgh in it called the SSVC or Stakeholder Specific Vulnerability Categorization.
• 54:44
  Speaker 0: And in fact I may even hit up my friends at ONAFSA to say what if were able to incorporate elements into our onapsis vulnerability findings, because what this will do is it says already in.
• 54:58
  Speaker 0: This is a drop everything and do-it thing like.
• 55:00
  Speaker 0: and here's why actually give reasons.
• 55:03
  Speaker 0: people are very reasonable in my.
• 55:04
  Speaker 0: well let me roll that back.
• 55:07
  Speaker 0: People can sometimes be very reasonable if you give them the right information to help then make an intelligent decision.
• 55:12
  Speaker 0: So If You say I've got this problem from this problem Like Here's Why We Are Calling This A stop The Presses Go Fix It Right Now.
• 55:20
  Speaker 0: I think if people understand the why, they're more likely to help you.
• 55:24
  Speaker 0: But If You just come and say patch this because i'm scared And I said so cuz im security Like I Think that's where you start to
• 55:31
  Speaker 2: really run into problems.
• 55:32
  Speaker 2: No, I agree with you on That.
• 55:40
  Speaker 0: Thank you.
• 55:41
  Speaker 2: Such a good point.
• 55:41
  Speaker 2: Cool!
• 55:41
  Speaker 2: Well we have time for one More question.
• 55:46
  Speaker 2: Yeah, so I'm going to do this one.
• 55:48
  Speaker 2: If someone in the audience is currently negotiating their rise contract.
• 55:53
  Speaker 2: what does one security requirement or visibility clause they should insist on including?
• 55:58
  Speaker 2: To ensure they aren't left in the dark after go live
• 56:04
  Speaker 0: with something that they need to push for like you know before that paper signed.
• 56:10
  Speaker 0: That's when you have all the power and an SAP has all sorts of security kind And I would get whatever you can possibly get out of that.
• 56:20
  Speaker 0: I would say, show me your list to add on and then give me everything that you've possible got.
• 56:25
  Speaker 0: Try and get all that built
• 56:26
  Speaker 0: in.".
• 56:27
  Speaker 0: You know...I remember when we first started talking they tried upsell for a next generation firewall which is wild because i was doing next-generation firewall stuff like city municipal worker in twenty fifteen.
• 56:42
  Speaker 0: the fact that S&P said this isn't an extra skew.
• 56:46
  Speaker 0: So, so take their list of stuff and say like why is this just not included?
• 56:50
  Speaker 0: Like we're spending millions and millions and billions of dollars.
• 56:54
  Speaker 0: Why are some of the stuff non-included?
• 56:56
  Speaker 0: you don't get that power after you've signed.
• 56:59
  Speaker 0: You only have that power before you sign And they are trying to get people to sign that paperwork.
• 57:06
  Speaker 0: If anyone really wants to get wild Go push for getting read-only access logs from their Azure infrastructure, whatever their hypervisor is.
• 57:17
  Speaker 0: If you are successful let me know.
• 57:20
  Speaker 0: I will buy you a coffee or beer or soda and i'll pick your brain because that's my holy grail of giving information to help defend the organization.
• 57:30
  Speaker 0: Awesome!
• 57:33
  Speaker 2: You heard Ian.
• 57:36
  Speaker 2: he just offered you drink or wine?
• 57:41
  Speaker 2: Yes, so we're gonna wrap up now.
• 57:43
  Speaker 2: Please go ahead and check out what we've put in the resource box over to your right.
• 57:48
  Speaker 2: there are a bunch of different white papers and things that can help you out And We're going to wrap-up this webcast.
• 57:57
  Speaker 2: thank you so much for joining us.
• 57:59
  Speaker 2: Thank You Ian and PK for such great insights.
• 58:05
  Speaker 2: we really appreciate your expertise.
• 58:08
  Speaker 1: We'll put Ian in the Expertise category, I appreciate that and I appreciate anyone who's spent their last hour with us.
• 58:13
  Speaker 1: so you know they're all busy.
• 58:15
  Speaker 1: thank-you
• 58:16
  Speaker 0: thanks everyone.
• 58:17
  Speaker 2: Thank You!
• 58:19
  Speaker 2: In a moment two questions are raised.
• 58:21
  Speaker 2: get pop up on your screen.
• 58:23
  Speaker 2: please take that And stay tuned for the post event email tomorrow With The Link to On Demand Presentation And please go ahead and share it with your colleagues.
• 58:33
  Speaker 2: Sharing is caring, thank you so much.
• 58:35
  Speaker 2: have a great rest
• 58:38
  Speaker 1: of.