You are looking at a target, the commercial story is attractive, and the deal team needs to know whether technology risk could derail the transaction. That is the practical job of cybersecurity due diligence for M&A. Not to produce a generic security report. Not to shame the CTO. Not to boil the ocean. The job is to tell the buyer what risk exists, whether it matters to valuation or deal structure, and what must happen before and after close.
In my experience, the fastest way to waste money on cyber diligence is to treat it like a compliance questionnaire. Questionnaires have their place, but buyers need judgement. A mid-market company can have imperfect policies, patchy documentation, and still be a perfectly sensible acquisition. Another business can have neat policies, a clean data room, and a material exposure sitting in identity management, customer data handling, or a fragile cloud setup. The work is to distinguish noise from deal risk.
The buyer question is simple: are we inheriting manageable operating debt, a remediation bill, an integration blocker, or a risk that should affect price, terms, or appetite?
What buyers actually mean by cybersecurity due diligence for M&A
When sponsors, operating partners, lenders, and corporate development teams search for cybersecurity due diligence for M&A, they usually mean one of five things.
- Can this target be safely acquired? The buyer wants to know whether there is an undisclosed breach, weak control environment, or critical dependency that changes the risk profile.
- What cyber liabilities are we inheriting? This includes customer data exposure, regulatory obligations, insecure infrastructure, privileged access issues, vendor dependencies, and incident response maturity.
- Will cyber risk affect valuation or terms? The answer may inform price chips, escrow, reps and warranties, insurance exclusions, closing conditions, or a specific remediation covenant.
- What happens on day one? The buyer needs a practical first-100-days view: who owns security, what to fix first, and what level of spend is realistic.
- Can we integrate this asset? In platform and add-on strategies, integration risk matters. Identity, data segregation, endpoint controls, and cloud architecture can either enable or slow the thesis.
That is a different exercise from a penetration test, ISO readiness assessment, SOC 2 audit, or vendor security review. Those can be useful inputs, but M&A diligence has a sharper commercial lens. I am looking for materiality, urgency, and buyer actionability.
Why cyber diligence belongs inside technical due diligence
Cybersecurity is often treated as a separate workstream. Sometimes that is appropriate, especially for regulated, data-heavy, or security-sensitive targets. But in many mid-market deals, cyber diligence is most useful when it sits inside broader technical due diligence.
The reason is simple: cyber risk is rarely isolated. Weak identity controls may be tied to a rushed cloud migration. Poor logging may be caused by cost pressure in infrastructure. Production access sprawl may come from a small engineering team moving fast without a release discipline. Legacy software may be both a product scalability issue and a security issue. If the cyber reviewer only sees controls in isolation, the buyer gets a list of findings without a view on operating reality.
I prefer to assess cyber, architecture, engineering process, data, infrastructure, and product dependencies together. That gives the sponsor a more useful answer: not just what is wrong, but why it exists, how hard it is to fix, and whether management can realistically execute the remediation plan.
A decision framework for M&A cyber diligence
I use a simple decision framework. It keeps the work focused and prevents the diligence process from turning into a theoretical audit.
1. Exposure: what would create material harm?
Start with the business model. A B2B SaaS company storing sensitive customer data has a different exposure profile from an industrial services business with a small internal application estate. A healthcare workflow platform, payments-adjacent business, marketplace, education platform, or identity-heavy product carries different obligations again.
The question is not whether the company has every best-practice control. The question is what failure modes would matter. Customer data leakage, ransomware downtime, fraudulent payment flows, credential compromise, intellectual property loss, or loss of regulatory standing do not carry equal weight in every deal.
2. Control maturity: are the basics operating?
I look for the boring controls first because the boring controls prevent a disproportionate amount of damage. Identity and access management. Multi-factor authentication. Privileged access. Endpoint protection. Patch cadence. Backups and restore testing. Logging. Incident response ownership. Vendor access. Cloud configuration. Data retention. Secure development practice where software is part of the product.
Perfection is not the bar. Evidence is the bar. Can the target show how access is granted and revoked? Are admin accounts known? Are backups tested, not just configured? Is there a real incident response path? Are production secrets managed properly? Can someone explain the cloud estate without hand-waving?
3. Evidence: is this documented or merely asserted?
In diligence, I put more weight on artefacts than interviews. A good management team can still unintentionally overstate maturity. I want to see policies, logs, architecture diagrams, insurance submissions, recent security reviews, penetration test reports, vulnerability scans, access exports, cloud account structure, security tooling, incident tickets, customer security questionnaires, and board materials where available.
Evidence also reveals culture. If the company has a pragmatic issue tracker, owners, and closure history, imperfect controls are easier to underwrite. If every answer depends on one engineer's memory, the buyer is underwriting key-person risk as well as cyber risk.
4. Materiality: does this change the deal?
Most cyber findings do not change the deal. They become part of the post-close operating plan. The important discipline is to separate findings into categories:
- Deal blockers: active breach indicators, undisclosed material incidents, severe regulatory exposure, inability to operate safely, or unacceptable customer contract conflicts.
- Price or terms issues: remediation cost, cyber insurance problems, required third-party assessments, escrow considerations, or specific closing conditions.
- 100-day actions: MFA rollout, backup testing, logging improvement, vendor access clean-up, endpoint hardening, incident response runbook, security ownership.
- Longer-term maturity: formal governance, compliance programmes, security architecture upgrades, secure SDLC, and board-level reporting cadence.
5. Execution: can the team fix it?
This is where operating judgement matters. A finding is only useful if the buyer understands the remediation path. Who owns the work? Is it a CTO, head of infrastructure, product engineering lead, external managed security provider, or an interim technology leader? How disruptive is it? Does it require new tooling, new process, new budget, or a change in behaviour?
I would rather give a sponsor five actions management will actually execute than a 70-item risk register that dies after close.
The diligence areas I would inspect
The scope depends on the target, but a serious cybersecurity diligence process usually covers these areas:
- Security governance: ownership, policies, board reporting, risk register, cyber insurance, incident history, customer obligations.
- Identity and access: MFA, single sign-on, privileged users, joiner-mover-leaver process, shared accounts, third-party access.
- Infrastructure and cloud: account structure, network segmentation, public exposure, configuration management, secrets, backups, disaster recovery.
- Endpoint and workplace security: device management, EDR or antivirus coverage, patching, remote work controls, mobile device exposure.
- Application and product security: secure SDLC, dependency management, code review, penetration testing, vulnerability handling, production access.
- Data protection: data maps, retention, encryption, customer data segregation, sensitive data handling, deletion workflows.
- Incident response: escalation path, tabletop exercises, breach notification awareness, logging, forensic readiness.
- Third-party risk: critical vendors, outsourced IT, MSP or MSSP dependencies, customer support tooling, offshore access, SaaS admin rights.
- Compliance and contracts: SOC 2, ISO 27001, PCI, HIPAA, GDPR, sector obligations, customer audit rights, security addenda.
The aim is not to become the company's permanent security auditor. The aim is to understand what the buyer is taking on.
Short comparison of diligence options
There are several ways to run cybersecurity due diligence for M&A. Each has a place.
Internal IT review
This is cheap and fast if the buyer has a strong technology leader with time available. It works for small targets or low-risk sectors. The tradeoff is independence and pattern recognition. Internal teams may also optimise for how they would run the asset post-close, not necessarily for deal materiality.
Specialist cyber audit
A cyber specialist can go deep on controls, tooling, and technical vulnerabilities. This is useful for high-risk targets, regulated industries, or situations where breach suspicion exists. The tradeoff is that the output can become too technical or too compliance-heavy for an investment committee unless it is translated into commercial implications.
Penetration test
A penetration test can identify exploitable weaknesses in a defined scope. It is not a full diligence process. It will not tell you whether security governance works, whether access hygiene is sound, whether backups restore, whether contracts create exposure, or whether the team can execute remediation. I see pen tests as evidence, not the whole answer.
Technical due diligence with cyber built in
This is the route I usually favour for mid-market transactions. It connects cyber risk with architecture, engineering, infrastructure, product, data, and leadership capability. The tradeoff is that it must be led by someone who understands both technology operations and transaction context. Otherwise it becomes a checklist with nicer formatting.
When cybersecurity due diligence is the wrong tool
Cyber diligence is valuable, but it is not always the next best use of time or budget.
It is the wrong tool if the buyer has not yet formed a clear view on the target's business model, data sensitivity, and transaction thesis. In that case, a narrower pre-LOI technology risk scan may be more appropriate. You do not need a heavy diligence process to discover that the target is too early, too undocumented, or outside the sponsor's risk appetite.
It is also the wrong tool if the goal is to certify that the company is secure. No serious advisor should imply that a short diligence exercise can guarantee security. Diligence reduces uncertainty; it does not eliminate risk.
It may be the wrong tool if management is not ready to provide evidence. If access to basic artefacts is blocked, the buyer may need to treat that as a process risk in itself rather than pretending a full assessment can proceed.
Finally, cyber diligence is not a substitute for post-close ownership. If the buyer knows the company is underinvested and plans to professionalise it anyway, the key output may be a practical operating plan, budget range, and leadership recommendation rather than a long list of findings.
Common red flags I would not ignore
Not every weakness is a red flag. These are the patterns that get my attention quickly:
- No clear owner for security, even informally.
- MFA missing for administrative access, cloud consoles, email, or critical SaaS tools.
- Former employees, contractors, or vendors retaining access.
- Backups configured but never restored in a test.
- Production access broadly available to engineers without logging or approval.
- Secrets stored in code repositories, spreadsheets, chat tools, or personal password managers.
- No record of incident response decisions or customer notification obligations.
- Critical infrastructure managed by one person with no succession plan.
- Recent penetration test findings with no owner, no remediation dates, and no retest.
- Customer security commitments that exceed the company's actual controls.
Any one of these can be manageable. Several together suggest a control environment that needs buyer attention before the IC memo is finalised.
What good output looks like
A useful cyber diligence output should be short enough for deal teams to use and specific enough for operators to execute. I would expect it to include:
- An executive view of material cyber risk.
- A ranked list of findings by deal impact and urgency.
- Evidence reviewed and evidence missing.
- Clear separation between closing issues, 100-day actions, and longer-term maturity work.
- Indicative remediation ownership and sequencing.
- Questions for legal, insurance, and commercial teams where relevant.
- A view on whether findings affect valuation, terms, integration, or post-close budget.
The output should not be a generic maturity score unless that score informs a decision. Sponsors do not need theatre. They need a point of view.
How I'd approach this
If I were advising a sponsor on cybersecurity due diligence for M&A, I would first calibrate the deal context: sector, data sensitivity, transaction stage, value creation thesis, management depth, and known technology concerns. Then I would run a focused evidence review across identity, cloud, infrastructure, product security, data protection, vendors, incident response, and contractual obligations. I would interview the technology and operational owners, but I would anchor the assessment in artefacts.
For an active process, the right next step is usually a focused 5-Day Tech Due Diligence review with cyber risk built into the technical assessment. If the sponsor is earlier in the process, or needs a standing second opinion before spending diligence budget, I would use a concise Written Brief to frame the risk, the evidence request, and the questions that should go into the next management session.
My bias is to keep the work practical. Find the risks that matter. Translate them into deal implications. Give management a remediation sequence they can actually run. That is how cybersecurity diligence earns its place in an M&A process.