Wednesday Wisdom: The Acquisition Problem. When Growth Arrives With Someone Else’s Security Debt

Two closed laptops on a charcoal table joined by one network cable, with a red-tabbed document folder and a brass key between them, under the title The Acquisition Problem

Acquiring revenue also means acquiring the operating environment and security history behind it.

A deal is priced on revenue, clients, and reputation. What actually changes hands is an operating environment with a history.

That history may include systems, accounts, data practices, outside providers, and decisions the buyer has not yet seen. For a family office, RIA, law firm, medical group, hospitality group, or professional services firm, that inherited environment can shape the first year of growth as much as the purchase agreement does.

This is not only a large-company M&A issue. A small firm that acquires a practice, a client book, or a new partner can inherit the same exposure, often with less capacity to absorb it.

The outdated lens treats cyber diligence as an IT questionnaire completed before signing, with cleanup deferred until after integration. The modern strategy treats security debt as part of the purchase: evidence before signing, risk reflected in deal terms where appropriate, and trust earned in stages rather than assumed on Day 1.

A business is valued for what it earns, while security debt hides in what it has been through.

Security debt is often invisible at valuation because it does not appear neatly in revenue reports or client lists. It sits in old systems, unresolved access, informal data sharing, and incomplete records. These issues can be difficult to identify through a generic questionnaire, especially when the seller has not maintained a complete view of its own environment.

That does not always mean the seller is concealing a problem. A smaller organization may have relied on a small team, outside providers, or informal practices that worked well enough day to day. The result may still be an incomplete picture of who has access, where sensitive information lives, or what happened during earlier incidents.

The Bare Metal Cyber article, "M&A Malware: Security Debt Hidden Inside Acquisitions", offers a useful framing: inherited security debt is broader than technology, and it can remain hidden in everyday operating practices.

The fix is... ask for evidence that reveals how the organization operates, not just statements that it has policies. Cybersecurity due diligence for an acquisition should begin with the services that matter to the business: how clients are served, how records are protected, and what must remain available for the business to operate. A network vulnerability assessment and a review of data backup and recovery services answer different questions than a policy document does, and both belong in the evidence pack.

The post-signature period is where cyber incidents can affect the deal's expected value.

In its March 2026 study, CISO Redefined III: Navigating Cybersecurity Risks in Transactions, FTI Consulting surveyed 100 CISOs, 78 heads of M&A, and 100 general counsel at U.S. public and private organizations with at least 500 employees. These are survey findings, not a prediction of what will happen in any individual deal.

Nearly 1 in 4 surveyed executives said they had experienced a cyber incident during or shortly after a transaction. In the same study, 42% reported significant deal value reduction, 58% said financial targets were impaired, and 20% said a deal was delayed or paused.

The study also points to an oversight gap. Thirty-four percent of CISOs said they were not heavily involved in transaction decisions. One in three CISOs did not believe they had authority to stop a transaction over cyber risk, or were unsure. One in four said leaders pushed to close quickly instead of conducting thorough cybersecurity due diligence.

The collaboration numbers reveal a further disconnect: only 17% of CISOs said collaboration between cybersecurity and corporate development significantly increased during a transaction, compared with 34% of general counsel who felt it did. And only 23% of executives said they proactively manage cybersecurity risks after close.

The fix is... bring security, legal, finance, and operating leadership into the same deal conversation early enough to influence decisions. For a smaller acquirer, the discipline matters even more: there may be less capacity to absorb disruption or rebuild controls while serving clients.

Security debt comes in four forms, and only one is primarily about technology.

The Bare Metal Cyber framing groups inherited security debt into four business-relevant categories:

  • Technical debt: Unsupported systems or weak authentication can make core services harder to protect and maintain.

  • Identity and access debt: Orphaned privileged accounts or third-party access nobody owns can leave unclear who can reach sensitive systems and information.

  • Data and privacy debt: Unknown data stores and informal sharing practices can undermine confidentiality and make it difficult to understand what information the buyer is responsible for.

  • Governance and legal debt: Unenforced policies and incomplete incident records can leave leadership unable to establish what happened, what was reported, or what obligations may follow. This is the category that can become a reporting obligation the buyer never priced.

These categories should not be collapsed into one score. A suspected active compromise calls for a different response than a legacy system or a missing record. Chennakeshav Adya's "Cyber Due Diligence for Deal Teams: Translating Exposure into Price and Closing Conditions" recommends separating findings into active compromise, control failure, regulatory exposure, technical debt, and integration-created risk. Each calls for a different decision.

The fix is... translate each material finding into the right deal response. That may mean additional investigation, a defined closing condition, a planned integration sequence, or a clear remediation owner. The right response depends on the evidence and the business impact.

During integration, simultaneous change can make risk harder to see and easier to spread.

The integration window concentrates activity. Both organizations may be changing configurations, mapping identities, opening connections, and extending work schedules. As Bare Metal Cyber observes, a suspicious anomaly can be dismissed as "just an integration artifact." At the same time, temporary exceptions can become permanent operating practices if no one owns their removal.

A weakness in the smaller organization could become a corridor into the larger one if access is extended too broadly or too quickly. The same question applies to outside providers: inherited accounts and third-party connections need an owner and a reason to remain.

That is why the trust you extend to others and the vetting you complete before extending trust matter when evaluating a target. The issue is not whether the other organization is trustworthy in principle. It is whether its access and operating practices are understood and appropriately governed.

The fix is... treat temporary integration concessions as exceptions with an owner, a business reason, and a review date. If no one can explain why an access path exists or when it should end, it should not quietly become the new baseline.

A checklist is not diligence, and "improve security" is not a controlled closing condition.

A completed questionnaire records assertions. Diligence tests those assertions against evidence. Depending on the deal and the services involved, useful evidence may include an asset inventory, access reviews, an incident chronology, and critical third-party contracts. The goal is not to collect documents for their own sake. It is to establish what is known, what remains uncertain, and how that uncertainty affects the business.

A closing condition must be objective and verifiable. "Improve cybersecurity" is not a controlled gate because it does not define what must change, who will verify it, or what evidence is sufficient. Adya's framework makes this distinction central: a useful condition describes a specific outcome that can be checked.

The fix is... define the evidence and the decision before the closing deadline arrives. For example, leadership should be able to identify the specific access, incident, or control issue at stake, the owner responsible for resolving it, and the proof required to confirm the agreed outcome. Deal and legal advisers can determine how that evidence belongs in the transaction documents.

This evidence-led approach also has to fit the sector. A wealth manager buying a book of business has to reconcile RIA cybersecurity compliance across two firms. A law firm buying a practice inherits client files and matter records. A family office absorbing an outside manager's arrangements inherits whatever access those arrangements created, which is why cybersecurity for family offices so often turns on inherited accounts rather than new technology. Much of the work falls to managed IT services for law firms or an experienced managed security service provider, and the technology is a support system for operational risk, client trust, and the ability to deliver the service being acquired.

Day 1 should follow observe, constrain, then connect, not assume and merge.

An acquired environment should be treated as untrusted until it demonstrates otherwise. That does not mean business operations must stop. It means the buyer should stage how much access and connectivity the acquired organization receives.

First, observe how the acquired environment operates and establish what is normal. Then constrain access to what is necessary while key identities, accounts, and connections are reviewed. Finally, connect systems in stages once leadership has enough evidence to approve the next step.

This approach should include ring-fenced identity, heightened monitoring during integration, and explicit go/no-go criteria for expanding access. Those criteria turn integration from a series of hurried exceptions into a managed business decision.

The fix is... decide in advance who can approve each increase in access, what evidence they need, and what would pause the next stage. A growth plan should not rely on full network connectivity on Day 1 simply because it is convenient.

The leadership test is whether someone can answer the same hard questions before signing, then at 30 and 90 days.

A principal or CEO does not need to manage technical details personally. They do need clear answers to questions that connect the inherited environment to business accountability:

  • Before signing: What critical business services are we acquiring, and what evidence do we have about the systems, access, data, and outside providers that support them?

  • Before signing: Which findings could affect the deal terms, create a reporting concern, or change the order and pace of integration?

  • At 30 days: Who owns each material risk, what access remains constrained, and what evidence is still missing?

  • At 90 days: Which temporary exceptions have been removed, which controls have been verified, and what remains open with an accountable owner and completion plan?

The human layer matters as much as the control environment. Staff need clear communication about new processes, who can authorize access, and where to raise concerns. A useful reminder is that trust starts at the front door, with the people and decisions that shape how the organization works.

The fix is... make these questions part of the acquisition governance rhythm, not a one-time diligence exercise. A fractional CTO or experienced security partner can help leadership turn complex findings into decisions the organization can own.

Buying a business, practice, or client book can create real opportunity. The modern strategy is to value not only the revenue coming in, but also the security history, operating practices, and access that come with it. Evidence before signing, risk translated into deal decisions, and staged trust after close help protect the growth the acquisition was meant to create.

If you are evaluating an acquisition or planning an integration, we can help you get clarity on the security questions that matter to the business. Start a practical conversation with Oram Cybersecurity Advisors.

Next
Next

A Practical Microsoft 365 Security Review for Boston Law Firms