PODCAST

M&A Cybersecurity Considerations

Join Ben Phillips, Director of IT Risk Advisory Services at KSM, and Cody Rivers, Managing Director at Reveal Risk, as they dive into cybersecurity considerations when it comes to mergers and acquisitions. They cover topics such as how to assess the current cybersecurity of a business, how cybersecurity can impact the valuation of a company, best practices for integrating IT security infrastructures, and more.

 

 

Listen wherever you get your podcasts!

Apple Podcast Icons_100x100    Spotify Podcast Icons_100x100    Google Podcast Icons_100x100

Highlights from the Podcast:

Ben Phillips - 2025 M&A Cybersecurity Considerations Podcast

Pick One Cybersecurity Framework

Ben Phillips, KSM

KSM - 2025 M&A Cybersecurity Considerations Podcast

Ask The Right Questions

Ben Phillips, KSM

Reveal Risk - 2025 M&A Cybersecurity Considerations Podcast

Assess Yourself Before You Break Yourself

Cody Rivers, Reveal Risk

Cody Rivers - 2025 M&A Cybersecurity Considerations Podcast

Have a Cybersecurity Incident Plan

Cody Rivers, Reveal Risk

Transcript

Adam Farag: Hello, and welcome to OnPoint, a podcast by Oak Street Funding, where we sit down with industry leaders to bring insights to the topics you want to hear about. I'm your host today, Adam Farag, Vice President of Strategic Markets at Oak Street Funding, and let's get on point.

Adam Farag: Today, I'm joined by Ben Phillips and Cody Rivers. Ben is Director of IT Risk Advisory Services at KSM CPAs and Advisors, and Cody is Managing Director at Reveal Risk. Today, we're going to be discussing cybersecurity for M&A. Ben and Cody, thank you guys for joining me today.

Ben Phillips: Thanks for having us.

Cody Rivers: Happy to be here.

Adam Farag: We're going to dive right in. To start, what trends in cybersecurity do you guys see emerging over the past several months, and what trends do you see going forward?

Ben Phillips: Awesome. Well, the trends, I think there's no shortage of news articles on attacks, breaches, and ransomware. I think there are a lot of corporate companies and a lot of companies in general trying to get their hands around the strategy of how to approach this. I think there's been a lot of spending historically on cyber, but there's also still some alignment to be done there. Staying up on trends, having a strategy, and knowing what your posture is internally are important. I think there’s a lot of focus on having a clear cyber strategy that you can talk about with most leaders and folks who aren’t in cyber day to day.

Cody Rivers: Yeah. We're seeing a lot of AI-powered attacks and continued prevalence of vendor attacks, including software vendors. Organizations have been implementing more of a zero-trust security framework, which is essentially “never trust, always verify” for devices that are accessing the network. I think those are a couple of things that are happening right now. For the future, to your point, AI technology is evolving quickly. Deepfakes, for example, have gone up four-digit percentages in the past two years because of what someone can do with a new iPhone that was released the other week. I think that enables attacks and social engineering, and with AI and everything, it just makes every attack easier. The unfortunate news is the good guys have to be right every time. The bad guys need to be right one time.

Adam Farag: Yeah. That's a good point. As we segue into M&A, how do you evaluate cybersecurity that's in place for a company that you're looking at, or that one of your clients is looking to acquire? How do you evaluate that?

Ben Phillips: Yeah. Great question. In general, the triad in cyber is people, process, and technology. Technology is more mature. It's evolving. There's a lot of focus on it. I think people and process are the two that are not quite there, and that’s where we like to focus because there has not been as much focus as there should be. Process isn’t the sexiest part of cyber, right? Paper, documentation, governance — those are the things that often get left behind. A lot of things to focus on are: is it documented? Is it repeatable? Does everyone in the organization know what to do? Do the people who need to follow the process even know where to find that process?

Cody Rivers: Yeah. I would say in your typical transaction lifecycle, it’s a lot of data about things that have happened in the past, and someone is evaluating it. Think of financial diligence. You get revenue metrics, AR metrics, general ledger information, and a bunch of stuff where you don’t need a policy, and it’s not based on a theory or thought. It just is what it is. We can do KPIs against that information. With cyber, when you’re doing it, it’s pretty important to make sure you ask the right questions. Some can be point blank: are you aware of any security incidents you’ve had in the last six months? What about the last three years? So ask a lot of those questions. Ask about leadership’s tone at the top as it relates to cybersecurity. Ask the folks responsible for security, “Do you have policies that you follow, or are they just policies that you have because you have to have them?” I can get a lot more from a 10-minute conversation with someone than I can get from spending a bunch of time reviewing a bunch of stuff. You just have to ask pointed questions because at that point, they’re in diligence. They have to be accurate. If not, I’m sure someone’s going to see them.

Ben Phillips: On the cyber side, aside from people and process, there are some easy buttons you can hit from a tooling perspective. You can use asset discovery tools. You can use information to identify past breaches. I would ask them about their vendors, especially vendors that are mission critical as it relates to third-party risk management. I would ask them what regulatory and compliance things they have agreed to. Think of contracts, SLAs, things like that. Sometimes during diligence, it’s really checking to make sure what the organization has agreed upon.

Cody Rivers: Yeah. To your point, when I’m looking at a company, I ask, “Is it written down?” Is it Tom in IT who says, “I’ve been here for 20 years, and this is what I do,” but no one else knows? If Tom is on vacation, what happens? If Tom isn’t here, what happens? If Tom was gone for a few months or just came back, what happens? Those things give you the level of depth. Then the supporting documentation can support that. In diligence, you don’t get a lot of time. You have to get in, ask a few questions to get an idea, and then if it moves past diligence into integration or close, you get more time. For folks doing M&A out there, this stuff trickles all the way down. Continuity and succession planning and having checks and balances in place as it relates to working with your clients also relates to your IT, cybersecurity, and everything else.

Adam Farag: As we’re talking about those vulnerabilities, when you're going through a deal, how do you guys help identify issues as you see them and unreported data breaches or cyber incidents when you're a consultant for a buyer?

Ben Phillips: Sure. On our side, we do a lot of these, so it’s muscle memory. We’ve seen a lot of different situations. In other areas, it may be a company’s first time acquiring another firm, or their second, or maybe they do a lot too. But oftentimes, the questions to ask are very specific. You ask what the auditor asks. You don’t offer up additional things. It’s knowing those questions to ask to say, “What may give me a peek under the covers or help me know what may be done?” You mentioned hidden vulnerabilities. Sometimes you can look at the balance sheet or something similar to see when they last had a big capital expenditure. Was it three years ago, five years ago, 10 years ago? How old is this equipment? That tells you about lifecycle management. There are things like that to ask. The role of a third party or a consultant is to bring that very pointed subject-matter expertise. I think of that parable where you pay someone to hit the thing one time because they know where to hit it.

Cody Rivers: A lot of times when we’re working with an investment banker, they’re representing the organization purchasing the company and making sure we have clear alignment on, “This is the stuff you want us to ask about. This is the stuff you want to know.” They’re not experts in this stuff, but we can ask the proper questions to identify what red flags are there. I think it’s important when you start at the tone at the top and when you’re talking to IT to say, “You have to tell them what they asked. There’s no hiding things here. This has to be all on the table.” If you ask the right direct questions, you’ll be able to say, “Have you ever had a breach recently?” or “Do you have an incident response program?” and then define what that means. It’s really about asking very pointed questions from someone who knows what they’re talking about or can identify what could be an issue.

Ben Phillips: From tools and technology, again, you can use systems and tools to track assets, passwords, and different things like that. But the point is having a playbook. Have a methodology and approach so you’re not just off the cuff. I think that knocks out a lot of the risk right there — following it so you don’t get in the moment and just say, “I think we’re good.”

Cody Rivers: Yeah. I should be on the sell side. I think about the spring break diet, right? “What can I do to look good?” Those are long-term things. Do the long-term stuff. But on the sell side, it’s important to say, “What are they going to be looking for?” because it’s the same question.

Adam Farag: Exactly. For sure. Now that we’ve moved into M&A, let’s talk about valuation. How can cybersecurity risks impact the valuation of a company during an acquisition?

Ben Phillips: This is probably one of the biggest unknowns in a lot of things because regulation and compliance is such a fast-evolving area that oftentimes the people doing the diligence may not be up to speed on the requirements, and they may not catch it. I’ll give you an example. CMMC got codified just recently. That’s the government side for some of the DOD contracts. If a buyer is getting a target company that may have DOD contracts and they need to be compliant with CMMC, if they acquire that entity, the entire company now has to be under that to satisfy those contractual requirements. That is not a cheap process. It’s documentation, process, and compliance. Those are things where, when you’re buying this company for X revenue and X talent, and as you acquire that company, you now have to either mature or make sure you meet the compliance requirements in that contract to maintain that revenue stream.

Adam Farag: For those of us on the webinar who don’t understand the acronyms as much, can you break down the acronyms a little bit?

Ben Phillips: Yeah, absolutely. CMMC is the government or DOD certifying body for NIST 800-171, which is a framework from NIST. CMMC is a certification or compliance framework on the government side. There are other ones. There’s HITRUST on the healthcare side. There are quite a few that depend on customer contracts and what those contracts require, and that’s probably the most important part.

Adam Farag: As it would relate to financial services, a wealth adviser, a CPA, or an insurance business that's working with highly confidential information, valuations are a hot topic in all three of those verticals. How do you think cybersecurity risks or problems could impact the valuation of a financial services firm? I’m not going to hold you to it. I’m just curious for my own.

Cody Rivers: I would say, think about the different regulations they have to comply with. For example, the FTC Safeguards Rule. If you’re looking at a company and they are not meeting those requirements, that can affect valuation because you’re going to need investment immediately post-closing. If they have shared passwords, never have backups, and kind of work off the cuff because they’re a growing organization, that will be a culture shock to a lot of folks within IT and also within the organization.

Adam Farag: You have to plan on that investment immediately post-closing.

Cody Rivers: You do have to plan on it.

Adam Farag: It heavily affects cash flow and valuation.

Ben Phillips: It heavily affects cash flow and valuation. You might do a little holdback.

Adam Farag: Yeah. Absolutely. So what are the biggest challenges or risks with cybersecurity during a transaction?

Ben Phillips: I think ownership. Based on the size, sometimes they are within a TSA, or transition services agreement, and sometimes at close ownership is very clear. It’s over and done with. Other times, the acquiring entity may have a large amount of stuff that needs to be transitioned. During a TSA, defining who owns what and who is responsible for what during this time of transition is critical. With ERP implementation or migration, if a breach does happen, whose responsibility is it? Does the target company still own it? Is the acquiring company responsible for it? How do the teams work together? What is the PR and communications side? What are the insurance implications? Some of that is navigating ownership and responsibility of incidents that could pop up and being clear so that when the incident happens, you are not developing that idea then.

Cody Rivers: Absolutely. Hidden breaches are another one — breaches that you don’t know about, and breaches that the organization doesn’t know about. Integration gaps are another. There is the cost of integrating IT and cyber on one playbook. Vendor evaluations matter too. Both companies may use different vendors. The acquiring company may have a certain vendor that makes their secret sauce. In a world where large organizations don’t want two vendors that do the same thing, someone’s going to have to drop a vendor. That can add operational risk. Different security cultures are also a factor. You may have one organization that, from a scale of one to 10, is a six, meaning they have the right tone and may not have the right budget, but they’re trying to do the best they can. Then you may have one organization that’s a three, where they don’t have the budget or personnel, and they’re just doing what they can to do their business. That is probably common in M&A.

Adam Farag: Usually, you have very lopsided situations, which gets into the next question. What are the best practices for integrating two completely different IT and security infrastructures? In a lot of M&A transactions, you probably see one up here and one down here, or vice versa. You don’t see a lot of the same, right?

Ben Phillips: Yep. I always say, “Assess yourself before you wreck yourself,” because you have to have a clear understanding of what the gaps are. Then I think of a RACI charter, R-A-C-I, which is responsible, accountable, consulted, and informed. For every piece of that, who falls in those columns? Because to your point, there’s so much going on. I have to have clear who owns this, who is responsible for driving it, who is consulted in the decision, and who we inform once the decision is made. I think “go slow to go fast,” but that’s on the integration plan. This is not what you do in diligence. In that time, you go very slow and methodical because you are affecting revenue. The reason this company was bought was to produce revenue and to have some kind of product. Once the papers are signed, the clock starts to either produce said revenue or get integration done. So having that defined upfront means that when you execute, you can go as fast as possible with minimal margin of error.

Cody Rivers: I would probably also add that on the cybersecurity or security side of integrating the two organizations from a cultural perspective, do yourself a favor and pick one framework. Pick the framework that most aligns to everyone because when organizations say they’re doing a hybrid or they’re doing a couple of things, that can’t be judged as well. It’s like saying, “I’m doing CrossFit, I’m going to the gym on my own, and I’m also doing this.” At the end of the day, you’re 30% doing each. Pick a measurable framework that both organizations, collectively as a whole organization, can align to, at least to start. Train your folks. Train your employees. It’s a people business. If people don’t do it, you can put as much technology as you want in place, and it’s not going to work. It’s important to ask for feedback. Knowing the different cultures of the organizations, organization B may need more support than organization A.

Adam Farag: How difficult is it to get buy-in from employees, and how do you deal with pushback from people who don’t want to change in those situations you’re talking about, immediately following an acquisition?

Ben Phillips: It’s a big thing. It’s very tough. Everyone has their own jobs. We call it organizational change management, or OCM, a lot of times, and it’s having an established OCM strategy. That’s not just about cyber or IT. Those are usually the ones involved, but there are other cultural things. It’s asking, “What is my way to disseminate this information to the workforce in a meaningful way that is effective and can be converted quickly?” It’s being clear on the why, the how, and the “what’s in it for me” type of thing. With anything IT, and especially in cybersecurity, you’re asking for additional effort from somebody. You have to be clear on why we’re doing this, how they can do it efficiently, and where they can get more information. It’s about having an effective OCM strategy.

Cody Rivers: I would also say making sure there’s active leadership support in what you’re doing. It has to start from the top. It needs to be on both sides. It can’t be, “Well, we’re doing this. We have to do it. Unfortunately, it’s going to cost us a bunch of money, but whatever.” That’s not strong support. This is more like, “No, this is important to the business. This is important to protecting our clients and protecting our revenue.” You also have to reward compliance. Incent based on what you want to see. It’s like anything else.

Adam Farag: Can either of you walk us through an example of an M&A deal where somebody did it right and how it should be done?

Ben Phillips: Yeah. Every deal is going to have nuance or challenges. It’s how you address challenges. I think setting or resetting realistic expectations is important. The challenge I sometimes see when it goes right is that a challenge has been uncovered, the team discusses a plan for it, resets the goal line of what’s going to happen, and communicates expectations accordingly. Instead of a November 1 date, maybe it becomes December 1. People may not be happy that it got delayed, but there are no challenges and no disruptions to business. It’s clear communication, setting realistic goals, and then measurement against that so everyone knows what’s going on. I’ve never seen a deal that just runs through with no bumps at all. There’s always something. But the challenge I see sometimes when it doesn’t go right is that people try to jam it or squeeze it in, something goes wrong in the end, and then they say, “I would have much rather just pushed back two weeks or a week and had it go smooth than try to jam it in a week before.”

Cody Rivers: For sure. I would say they did some sort of IT or cyber diligence, so they had the facts they needed before they signed the pieces of paper. From an integration standpoint, they didn’t just do it on day one. They planned for it tactically with different feedback. After integration, they made sure there was clear communication as it relates to: when do we align policy? When do we align cybersecurity posture? What does that roadmap look like? They didn’t just throw it on someone and say, “All right, go do this.” It involves a lot of different stakeholders — operations, IT, HR, finance. If the organization feels like they budgeted, they were aware of the relevant information they needed to have to make the next two years work or operate smoothly, and they didn’t lose a lot of personnel because of surprises, then the deal went well. If not, then there are always things that happen.

Adam Farag: Yeah. Well, thank you guys both for being here. I'm sure our viewers learned a lot. I know I did, so I really appreciate it.

Ben Phillips: Thanks for having us.

Cody Rivers: Thank you.

Adam Farag: Thank you all for listening to OnPoint, a podcast by Oak Street Funding. I'm Adam Farag, and tune in next time wherever you listen to podcasts as we get OnPoint. Don't forget to follow us on Instagram, like, subscribe, and leave a review.