Video: Your GRC Platform Is Only Half the Answer. Who's Helping You Run It? | Duration: 3017s | Summary: Your GRC Platform Is Only Half the Answer. Who's Helping You Run It? | Chapters: Welcome and Introductions (50.5s), Role and Distribution (212.58s), GRC Organization Variability (285.145s), Webinar Overview (372.165s), Proof Ready Program (568.25s), Recommendations and Launch (713.61s), My529 Onboarding Experience (831.44s), Overcoming Adoption Challenges (1097.14s), Policy Hub Integration (1284.55s), Advisory Services Value (1561.18s), Peer Exchange Forums (1891.93s), Vendor Risk Reliability (2153.95s), Benchmark Reports (2372.84s), Continuous Adaptation (2530.335s), Closing Remarks (2653.21s), Closing Remarks (2934.305s)
Transcript for "Your GRC Platform Is Only Half the Answer. Who's Helping You Run It?":
Hello, everyone. This is yet another GRC webinar, brought to you by Mitratech. The idea is that your GRC platform, if you have one at all, is only half the answer. And the the answer the answer to that question is, of course, who will help you run it? And we have, somebody that we really look up to, really respect in the GRC space. That is Robert Beckstead, and I'll ask you to introduce yourself first. But, the audience, now that you're with us, let's warm up a little bit. We have a poll question. We would love to hear from you. If we look at the share of your week that goes to GRC, how much is that actually? While we're waiting for the results, Robert, would you mind, introducing yourself already? Absolutely. I appreciate your time spending with me today. I appreciate being called an expert as well. I know that sometimes we, feel like we have a long ways to go, but I appreciate how far we've come, obviously, together and continue to build that. But, so I have been with my529, in the great state of Utah and The United States for about seven years. And four years ago, we decided, as a maturing organization, although not large by, employee population, that, we still had a fiduciary responsibility to our customers, etcetera that we mature our risk management program. With that in mind, we had been using in my, main role as director of information security a spreadsheet, and that spreadsheet would provide us, with an opportunity to discuss risk, and controls. Obviously, a spreadsheet only takes you so far, but, we wanted to take that a little bit further. And so we've we've obviously gone with various tools over that next four years. We've been with Mitratech for about a year now and, have been, pretty happy with where things are going. But, you know, my529 is a is a great organization, and we, feel that we're moving in the right direction with our GRC program. Yeah. Thank you so much for the introduction. Thank you so much for being with us. If we look at the outcome, the results are coming in. We see that it's pretty evenly distributed across, it's everything I do. It's a lot or it's one of the many hats I'm wearing. How how how would you position yourself? And if we look at this, these results from the audience, are you surprised to see it so evenly distributed? Not terribly surprised. For myself, it is about, fifty fifty. But, again, with information security, I deal with the aspects in that realm under risk management principles as well, and that's kind of why I got put in the, enterprise risk or GRC role, to kind of expand that to the whole organization. So I guess the the concepts I'm still applying generally, to both the cybersecurity realm as well as organizational risk. So I I think that's, pretty helpful pretty helpful to know. Yeah. Thank you. So to be honest, it really depends what what we're seeing in in the market. It depends very much on the type of organization, how much GRC makes up, of of... Consists of somebody's time. We see that there are organizations with armies of GRC people. Sometimes you speak with two people who say, well, we are basically, the entire GRC in this organization and everything in between. So then it it it really depends, and it changes the narrative on how you tackle GRC topics. I see that we have a first question that already came in. Thanks for finding, that q and a possibility. Yes. There are slides. I hope you're looking at them. Yes. They're also available, and I'm pretty sure one of, our colleagues will be able to send them to you or share them with you after the presentation. And we see in the bullet points that we have time for q and a at the end of the session, but we also really want to be agile. If there's anything on your mind that, you would like to have addressed, that you want to share maybe with us, as you see, this is all happening live. Please do not hesitate to already submit any comments, questions, suggestions in the q and a because we we we can see that's coming in live as well. What we'll be covering today, we have the total webinar will be less than an hour. Not too much less. I I hope there's so much to discuss, but we'll not go over. We want to discuss what actually the gap is between having software and what the GRC role actually consists of, and we'll realize there is a gap and how can we fill that gap. We think that advisory is, for example, one of the aspects, that can partly fill such a gap. And then, we'll very quickly pivot to the very pleasant cooperation we've established with Robert and his team on how Indeed we, based... Mitratech, based on what we've seen happening in the market, can hopefully support him, fill a couple of other gaps that he has or had, or at least provide some benchmarking. It's always nice to see that you're doing well or where you can improve. And then finally, we'll make it really practical and explain the audience how to engage with Mitratech. And engaging means not just, listening, to how great our software is because it is, But we also believe that actually beyond software, there's a lot of great software out there. And beyond just software, it is so important to be able to speak with people who've been working in the GRC space for a significant amount of time and maybe even more importantly, who have insights in what over 8,000 organizations have been going through regarding GRC topic. With... From that belief with that belief, we've built the Mitratech Advantage with a capital a, and the idea is that, indeed, we have those people internally that you would typically have to look for externally. They call themselves consultants, and they often are pretty expensive. We thought, well, we have those people internally, people who've been working on new regulations, new standards, who are in touch with many organizations regarding their GRC experiences. And why not connect all those insights that we get as a leading vendor with prospects, with individual customers. And that's how Mitratech Advantage was born. The idea is that you, as a customer, are fairly unique. On the other hand on the other hand, not that unique, taking to account you're one of over 8,000, and that actually really helps you to learn from what others have been going through, which regulations, for example, are applying to you and not just applying, but how to apply them in an efficient way, which regulations to prioritize over others. The bottom line, and that's what's meant with proof ready, make... Or help help you make sure that, we have those benchmarks available for you that we can let you know how you are performing from a GRC perspective, against others in comparison with others. And we've we've we've launched this program some time ago. We've already had a lot of positive engagements, positive response from organizations. They typically don't believe they're waiting for the invoice. They don't believe we consider this part of the SaaS offering. And very often, they also say, well, it's it's difficult to get these kind of insights, if I speak with peers or especially with competitors. I would never get these insights from them. And, of course, we never give, we never provide personal information unless there's consent on both sides. It's all anonymized data. They're anonymized trends, but enough to make sure that you understand where you're standing and where there's room for improvement. We put this quote on the page as well, on the slide. We... There are various of them, but we didn't want to make the funds too small to fit in all of them, so we took out one. The bottom line is that, you will have the support beyond the technical support. You, of course, always have an account team, but that account team, if you indicate or they indicate that there's an opportunity for advisory, they can they can, activate, they can loop in that Mitratech advantage team. The next aspect is the connection. We think it's really important if you want to become part of peer working groups. And, again, only if you want. There are people who are part of the customer advisory board, if we... As we call it, their entities that say, well, we just follow the webinars. There are other entities, other organizations, customers who are saying, no. We really love to meet in person at Mitratech events and exchange insights there. So we really try beyond the technical developments to maintain that exchange from a thought leadership perspective. And then finally, the advice. And as a lawyer, I always think the word advice is a red flag, so I would prefer to call it recommendations. We are able to basically address any topic that was raised or should be raised by our customers, and say, well, we we run the data. We see the trends based on what we've seen, what we're hearing across other accounts, and this is what we recommend you to do. And we are sometimes even surprised on what it surfaces. It's probably because of the very large data pool that we had... That we have at our disposal that these kind of advisory reports or recommendations are pretty spot on. And then the launch, of course, the idea is that, once you decide to work with Mitratech, it's not as if you just bought a Formula one race car, and we wish you the best of luck, with your first round around the track. It's actually you are getting the support that you need to make... To get the most out of that, incredible software with all its possibilities. And not just out of the software, itself, but also adjusted to the specific needs of your organization. And, typically, they're questions of where do you start, what what is, internal... What are internal policies that you need to think of, where will the board be interested from you to hear about how you're progressing, what to measure, etcetera etcetera. And then finally, the enablement, we, of course, also cover not just by on demand training, but also having a help center available to make sure that where you start is just the starting point, and you can build it out from there. Robert, I'm preaching a lot, but is this even a little bit, how should I say it, true to what you've experienced when we onboarded my529 as a new customer? Absolutely. No. I... There's a lot to reinforce there. As I mentioned, we had started with a spreadsheet. We'd gone to another tool. My team, even though we we manage, a good amount for our customers, we do so with a pretty lean staff. And so my risk staff is myself and another individual. And, our risk component, right, would, entail third party risk management, of course, the, risk register itself. We also wanted to bring in, policies and connect those better to our risks. And we had we had a tool before, because, again, with that number, we felt that we needed something besides a spreadsheet that we could evangelize throughout the organization. And relatively quickly, we we thought that we had vetted them out and had some great requirements defined. We discovered that the tie ins and being able to link those aspects together and pull information from where we wanted to was a little bit lacking. Yeah. With that in mind, we... When we set out to to find a different tool and found Mitratech and, really have appreciated, the linking of that. Now as you mentioned, Jan Stappers, before, absolutely, size of staff and, needs according to those numbers or at least the ratios to the rest of the staff. Right? We, wanted to take the time to put that information in, you know, to Mitratech. But, obviously, making that usable for folks is important to us. We we don't like blowware. We don't like tools that sit on a shelf. Obviously, spending, budget and and, again, money that we could use in in other aspects, wanted to make that more effective. Now, we have mentioned many times to our account manager, right, how much we appreciate, again, the integrations, and what we're trying to do and our goals, again, with limited staff. And she had mentioned, yes, in me... Meeting with yourself, Jan, your advisory. And we have, met a couple of times. Right? And we were able to give you information as to our situation, able to provide, right, kind of some information based on organization size and and basically what I've told you here as well as specific goals. And, yeah, the report that we received was very helpful as to here's what I heard, here's some action items as to what we think we can do going forward. I think one thing for that I'd I'd wanted to mention is that we had a concern again about making this really applicable to the whole organization. And oftentimes, right, you present information in a risk tool or GRC, and it's still a little ethereal. And making it real numbers is is important to us, and that's one of our our main goals right now. And, one of the things that stood out to me in the report, Jan, is taking those numbers and making them applicable to things that it applies to, versus kinda taking a whole tool approach, if you will, to the whole thing, but really emphasizing where that can be useful. You don't need to spend a ton of time on risk. Obviously, that isn't effectual, right, in in measuring that. And so help... Yeah. We we thought it's been very helpful to point out, Yeah. You have this goal. Let's work with you on maybe ideas how to how to make this or augment your staff. And, that's been important to us. Yeah. That's great to hear. Thank you very much. So, actually, if we if we look at that point, the the gaps, you you... At a certain point, you decide, well, we can do better or we should do better. Can you can you summarize, can you elaborate for the audience on what your organization was actually trying to improve? What were... And let's let's let's make this into two questions. One is, what was the trigger or the triggers to actually start looking at professional solutions? And the other one was, where did that friction that you wanted to get away with, or or the friction that you wanted to get rid of, where did that show up in the program? Yeah. I think our main friction was in getting folks to buy in not only to, a program itself, but to their involvement in it. Obviously, having a tool, again, kind of that blowware aspect. If we as a risk department use that, that's helpful for us. And the scope of that is the two of us in our case. The efficacy of the GRC and a risk program and, right, it's effectively an enterprise risk program, is to have the enterprise participate in that. Our previous instance was confusing, didn't have a ton of buy in. And, actually, once we went for renewal, folks were, even debating still, should we just use a spreadsheet? Which, right, after spending some time on, meeting with folks from around the organization, various departments, it's a little frustrating to hear that, right, that the the buy in wasn't there. Once we have communicated this information and, are, taking what we've learned from the advisory services as well as from Mitratech itself. Our employees are more engaged. They can see the effect of it throughout the organization. Our next step in that is making sure that we get a complete, or more complete picture of risk that folks can refer to on a more regular basis. And so we have some steps, that you have recommended, John, in order to, continue to improve on that. And we're looking to, again, have folks really be engaged on a more regular basis, so that the program itself is effectual, not just a tool, and leading to better business decisions, better risk decisions. And folks can perhaps, right on their own, say if I, wanted to do a particular activity, this is, you know, what it would affect, and they'd come to us versus us having to go to them. And so really driving engagement is important for us, and they've seen that friction, drop a bit as we have, engaged them with the Mitratech components. We've had positive review, and positive feedback from those folks and and continuing to drive that, regular engagement. Yeah. Thank you very much. I think that engagement is really, really important indeed, because without it, as you say, there is just another program or another tool, and it's there. You're paying for it, and that would be really, really a pity. If we look at the Mitratech Align, Mitratech Policy Hub, you've you've implemented those solutions. Which parts of your GRC program are actually now better structured after using that tool? Because various organizations might say, well, it is structured already. I'm just bringing in more complexity if I bring in tools. How did you experience that? Yeah. It actually feel the... It is nice to feel the opposite to that. Before our engagement with policies in general is pretty fragmented. You have policies in various places, under various auspices and responsibilities. We had a policy option that allowed us to have periodic reviews, but those periodic reviews again were fragmented. So in this case, with Policy Hub, we're able to review those concurrently, kinda like, you would be able to on a OneDrive, but a little more secure as well as have some, formatting to that in in the, way that it's distributed and comments are received, and we manage a workflow. The all... The other benefit to that and having multiple tools or multiple components of the tools that we can use those again throughout the implementation. So the GRC components as well. It's very convenient to be able to refer. Again, I mentioned before about the experiences before with other tools is that you, are not able to draw upon other other parts or other components. And so making this a a tighter integration for us allows us to, for example, use a policy as a control, and in those aspects, using the policy as a control helps people to see and and get to that directly versus, kinda guessing as to what the context of that policy is. Yeah. That makes sense. Thank you very much. If we see... I mean, if we if we look at, the situation after, the implementation and the organization decided to buy certain software, typically, the focus was a lot on the actual, actual actual choice of the software, lot of technicalities. At which stage... And I'm just rephrasing this question. As... At which stage you as an organization start thinking, okay. This is... These are the technical aspects that we want to put in place, but which other software elements do we have to put in place? With other words, how do we make sure that that glue that connects the organization to the software, is applied in a most efficient way? How do we get the most out of the software knowing that the software can properly do it, but how should we do it from a regulation perspective? What are others doing? These kind of questions. When this, these these kind of, topics come up in your organization? You mean when do we discover that we would need more help or. kinda some. That's that's a good angle. beyond. our own? Yeah. Thank you. Yeah. Absolutely. No. You know, being able to work with the management team, right, for Mitratech, like you're saying, gets our our software to a particular point. And we, as I mentioned, we did have requirements, that we had developed over time that we wanted in a tool. And those requirements really drove to, that engagement and wanting it to be an effective instrument for us. So we kinda knew beforehand. But to your point, right, taking that because our understanding of the tool is, from, I wouldn't say rudimentary, but a basic, understanding of here's the operations of it. I I think that, you know, in our conversations with our account manager over time, we just felt like, you know, we're at a certain point with the software itself and with the integrations. Here's some things we would like to see continue to develop, that, they... I think together we saw that something additional was needed in order to make... Kinda connect the dots, if you will. And, we... When she proposed that, right, we jumped at that opportunity to say, yeah, we're... We we want this engagement. And the appreciation for, yeah, not leaving it as it was, not status quo, I think is pretty telling as to the organization as well as, write the software is that we feel like and and see the evidence of that working together attitude that, yes, we want to engage with you. We want to learn from you, and we want to provide insight as you've said. Right? Benchmarking information, being able to share those best practices, really stood out to us and, we've used that engagement, right, hopefully, to our benefit, and, hopefully, maybe or perhaps our experiences can help others as well. Yeah. And and that is... Well, that that is really the nail on its head. It's ideally very much a two way street that we have so many customers. We can provide insights. But with every new insight that you provide, you want to be challenged, of course, by the organization because there there might be still a unique use case, a unique challenge. So that is definitely really, really appreciated. I'll skip this, topic because, actually, it's... It overlaps a little bit with the previous one, why does advisory matter alongside the technology. And I would like to move on to the poll question for the audience. Would you... And this is no strings attached. Of course, we're working towards... Well, in that case, reach out to us. We'll be very eager to hear from you whether you think that a conversation about your program would help. We would love to hear from you in that regard. And this is maybe also a question that, yeah, people say, yeah, it would would be nice. Yeah. I'm not sure what it would consist of. I'll be very, open in this. We sometimes even get requests from organizations who tell us, well, tell us what we likely should be worried... Worrying about. Tell us what others have indicated as main challenges. So, even those kind of first questions are, of course, possible. There is no maximum to a dialogue to the amount of reports or insights that you request, to receive. And and, again, sometimes organizations even need to determine or like to determine what should be on their radar or what's on the radar of other organizations. And I think this is really nicely reflected in the outcome of this poll where the great majority says, well, I would love... Or I'm rephrasing too much maybe. Yes. Maybe a conversation about your program would help. So thank you for providing those insights. Yeah. And then I on. the next slide, No. we have... Oh, sorry. Please go ahead. Robert. Yeah. No. Yeah. I mean, I've I've been in this industry for some time, not just GRC, but cybersecurity. And, having an organization invested in not only the effectiveness from a technological standpoint, but an effectiveness from a programmatic standpoint, and enhancing what we can do on the ground is is, very helpful. So Yeah. Thank you very much. and unique. So the... You know? We we, that... That's what we try to be. If we look at the report, that's, of course, Mitratech with the organization. What we also think, and and I raised this before, that more and more organizations, are saying, well, I would actually love to exchange with peers. And that's why we believe that we, should facilitate that kind of exchange outside of the typical conferences, outside of the, again, commerce included semi sales pitches. We should actually exchange that kind of, we should facilitate that kind of exchange between peers where there is time to speak about best practices, challenges. Typically, these take place under Chatham House rules. So what is being discussed is never being attributed to specific individuals or organizations. It really gives a platform to test where you are, see what others have been seeing, what you maybe have missed, and how others have been addressing these topics. So, here we have also another poll, and this will help us to understand to, see what the the interest for this kind of, initiatives is amongst the audience. Already lots of positive votes coming in. We have sessions, at your disposal, so please just let us know if you're interested in joining such a session. And then, Robert, to you, have you in the past, tried to set up or found certain forums or platforms where you can indeed exchange experiences with, colleagues in... I mean, colleagues with people with the same expertise in other organizations. How how did you how did you approach that? Yeah. We have, by virtue of being a, state organization, we have opportunity to participate in state information sharing groups and and find a lot of value in that. And that is generally from, the cybersecurity perspective. Other tools and things that we've implemented, have user groups, as you have mentioned. Mitratech having one. But the involvement of them, is generally tried to be seen as hands off, versus having some guidance to it, which in some cases helps. I think in the case of a GRC where it has opportunity to affect, big decisions in an organization, to have visibility throughout an organization, I think being able to have ideas bounced off of those who have been there before, and have an actual larger group of experienced individuals that would be willing to share their insight and opinions on things is very valuable. I was able to attend the Mitratech conference and and participate. And the attendees there were all very willing to, share insight from large, relatively large, companies. And no one no one has pretenses, if you will, as to, we're doing everything the right way, or the only way. And I think that humility as well as, desire to improve is, indicative of a good group of individuals. I haven't seen that in in all groups in the participation level. Right? And the engagement says something about how, again, the advisory component of this is is building into, right, that information sharing consortium, and, it's very valuable. Yeah. Thank you very much, and thank you audience for casting your votes. Then we'll move on with the deck. We have also, a last... We've seen this one already. I'll move on to the next slide. This is actually very practical how to engage, if you scan the QR code and you're interested in booking an an advisory conversation or, if you're, whether you're a customer or no customer yet, you can always use it. Please let us know that you're interested in something beyond the actual technical aspects of software, and we are here from you. If we look then at q and a, we already had questions coming in, and one of them is... Let me look at my other screen. What would make a vendor risk answer reliable enough for you to act on it? This is a question that we... This regards to reliability, of course, of information received. Robert, if if... So this is apparently one of the things that the audience is questioning about or wondering about if we would make a vendor risk... What would make a vendor risk answer reliable enough for you to actually act on it? Which which components or depth of information would it require? Yeah. It's... When you're looking at vendor risk, you have a lot of kind of the same thing as in GRC in general, the fear, uncertainty, and doubt. Being able to take out some of the sensationalized information that you might be receiving. So the more factual information and perhaps the more technical information, of course, the reliability of the source itself. If it's quoting, somebody or something else, there has to be some validity to that. There tends to be... If you're looking at the third party from an objective standpoint, everybody has a little bit of, bias, perhaps, and being able to filter that out and to get down to what needs to happen for your organization, if it's applicable, is very helpful, of course, as well in determining kind of the next step in the actions or at least the, emergent nature of of the issue itself. Yeah. It's obviously important from a third party aspect to know the integrations that you have with those third parties. It it might not be direct, for example. How how deep do you need to go? Having an s bomb or what what have you, being able to understand again those integrations and and tie ins to quickly ascertain if it's it's applicable to your situation. Yeah. And and so this is a very practical use case. And now I want to bring in the the benchmark because we can provide benchmark how others have been tackling this. Which aspects would you be most interested in to hear how the market or your peers have... Would have answered the same question. Yeah. Absolutely. It is helpful. Again, having experience is one thing, and it sometimes can make you a little myopic and, being able to oftentimes it may just be a reminder as to, oh, I need to I need to think about a different way of of doing that perhaps, or, oh, that would complete, this aspect of my program a little bit better. But absolutely, I don't take anything for granted. That's why that information is helpful to begin with. Right? Being able to make that determination. But absolutely having, again, a group kind of insight to that, we may overreact at times to certain information and having a group to vet that information out is absolutely helpful and that's definitely valuable. And, obviously, being able to trust those individuals, so it wouldn't be something that relationship would, not be built in a moment. Right? Being that trust is is built over time. Yeah. And and I'll explain for the audience how such a benchmark report would work. Of course, we would explain how large the n is, the the amount of, inputs from organizations that, the advice is based on, the benchmark is based on. The benchmark would typically take different angles, not a single, let's say it will never pretend there's only one way of approaching, whether it's third party risk management, supply chain due diligence, maybe very practical aspects like how do we make sure this new culture of compliance, of ethics is actually being lived in the organization. It can really be anything. A question that comes up very often is, what do others report to the board regarding GRC? So a a a lot of topics that we can have separate webinars about, but what the benchmark report does is it checks for signals, that were raised during conversations with other organizations, what kind of organization that was, and we basically profile it in order to make sure that the output is as relevant as possible for each receiver of the report because each report is created in a bespoke fashion. If... Robert, I'm I'm looking at the time. We still have a couple of minutes left, and and maybe one or two questions. What would you tell a peer who thinks that actually software enough is enough, that the... A peer who who says, well, I I... I've been in this, expertise. I've been in this function for many years. I know the drill. I just need the software, and I'll be fine. What what what would you tell them? Boy, the industry, the business environment, of course, AI is always a term that gets thrown out there. Everything that's going on, everything that changes quickly, some slow, just have a hard time imagining that just a tool by itself and you know the end of it. Obviously, we we change tools. We change approaches. We change, understanding based on information we gather. And I think if you're not willing to take in additional information or, look for different ways to do something or to refine your approach, it's, is it Lee Iacocca if you're not if you're not, moving forward, you're gonna... Getting behind, or something like that. That... Right? If we're not progressing, if we're not asking questions, if we're not thinking about how these various aspects apply, to our programs, to our tooling, Alright. We're gonna get left behind. If... Right. It... It's not just a tool. Right. It's the the approach that you take and, without being condescending, hopefully, make it appropriately known that absolutely that you don't want to be stagnant in your approach. Yeah. Thank you. I'll move to the last question because it's... I like that question. It's a little bit, it's a little bit challenging us, and and I'll put back this slide. Maybe there are people who say, well, actually, let's let's see what happens if I indeed request for this advisory engagement. The question is, what would a Mitratech advisory, trajectory differ from... How would it differ from the... A big four or a Mitratech GRC, expert advice? And my answer will be a very Dutch answer. Maybe, first of all, it's for free. That is already very attractive for us being Dutch. But apart from that, we have a unique position, and I don't say we're the absolute only people on earth, but we have a quite unique position that we have direct insights in over 8,000 organizations who we happen to have as customers in the Mitratech GRC space. And that is quite unique because even if you look at the very largest of, consultants, for example, they have many more clients or customers, whatever they call them. But it's unlikely that there is a very specific group who deals, who have insights, who has insights with a very large number of them. Typically, those kind of organizations are specialized around specific sectors, or even specific jurisdictions, and it might be difficult to find the the very, how should I say it, very flexible angle that you might be looking for. So for example, we've been doing these advisory trajectories with organizations that are a couple of people in the public sector, active in one jurisdiction. But we've also done it with multinationals that have internal army of GRC professionals, and they still really valued the multidisciplinary, multijurisdictional approach that these kind of reports and advisory processes could take. And so we can pivot really easily, and that is only because we have so many different customers, and this is our bread and butter. There's virtually not much that we can do outside of GRC SaaS and everything related to it. So I think those are the main differences. They're definitely GRC experts who've seen it all, who've spoken with everyone. And then, again, I think the price tag is also different And, of course, maybe the availability of those people, we are here for you. We've never said, sorry. We have to decline your request because we have too much, with too many requests. We really think this should be part of the ongoing relationship between you and the GRC SaaS vendor. Robert, we're we're almost, at the end of this webinar. Is there anything that we should still add for the audience, any insights, last comments, thoughts, warnings, encouragements, anything? Yeah. No. I mean, kinda emphasize what you said about the the big four. From a customer standpoint, I look at the big four and I think, well, they have something else to gain. Right? There's maybe not their focus. They might not be... I mean, they may be the expert in in risk management, but they might not be the expert in doing risk how we want to do it. So I think what we've experienced in having a voice in your area, Jan, that, it's more personalized, more, invested in our success as a program using Mitratech, and and using that investment versus, having them come in and and perhaps give just generalized advice, we can get some pretty specific, information as to here's here's how we see the product being used as well as, kind of that, integration with the organization in order for you to be programmatically successful. As you're saying, right, the kind of the experts not only in GRC, but in what we have implemented. I think that's very beneficial. No. The... I don't think I've left too much out. The, thing I would say beyond that is, you know, we we don't think that that's the end. Right? You know, that that we... Yeah. We've we've met with you and we have the information, but we also have the opportunity to, continue to refine that with you or to ask for that advice. And so it's not a one and, done. We we appreciate the relationship, and we appreciate the continuation of that advisement. Yeah. Thank you very much. And we appreciate your time for being with us today. Robert, Beckstead, thank you so much for sharing your insights. Audience, thank you so much for being with us today. Well, there are plenty of opportunities to further engage, to continue the conversation, or start new ones. So we would love to hear from you. For now, I'll thank you again for your time. Looking forward to staying in touch, and I wish you a rest... Very nice rest of your day wherever you are. Thank you. Bye bye.