Cybersecurity due diligence is the part of a deal review where a buyer tests how well the target business protects its systems and data, and what hidden cyber liabilities it might carry. Buyers ask for evidence of controls, incident history, vendor risk and compliance. Sellers who gather that evidence before going to market keep more control over price and timing.
This guide explains what gets reviewed, what documents change hands, how findings turn into price and contract terms, and how an owner can get ready well before the first buyer call.
TL;DR
- Cybersecurity due diligence checks a target’s security governance, controls, incident history, data handling and vendors, instead of relying only on what the seller says.
- Unresolved findings tend to become escrow holdbacks, price adjustments, closing conditions or extra indemnities.
- Buyers usually have a short window, often a few weeks, so organized evidence speeds a deal and protects value.
- Sellers should start preparing two to four quarters before going to market and fix gaps before buyers find them.
- Regulated sellers, such as public companies and government contractors, face extra disclosure and contract checks.
Table of Contents
- What cybersecurity due diligence means in a business sale
- What buyers examine in a target
- How the process runs and how long it takes
- Legal and regulatory items to review
- How findings affect price and terms
- How sellers prepare before going to market
- If you are the buyer
- Get your business ready for buyer scrutiny
- FAQ
- Sources
What cybersecurity due diligence means in a business sale
In any acquisition, the buyer inherits the target’s systems, data and past mistakes. Cybersecurity due diligence is the structured review of those risks. It looks at risk governance, defensive capabilities and key controls, and it is meant to go further than seller self-disclosures, according to Kroll’s practical guide published in 2025. The findings feed valuation, negotiation and the plan for the first days after closing.
It is not the same as general IT diligence. IT reviews often focus narrowly on hardware and technology documentation, while cybersecurity is a separate risk category that deserves a deeper look at systems, servers, networks and data processing.
Why buyers take it seriously
The most cited example is Marriott’s purchase of Starwood. Marriott announced the acquisition in 2016. In November 2018 it disclosed that attackers had been inside Starwood’s reservation system since 2014, exposing personal data of up to 500 million customers. Marriott did not catch the intrusion during diligence and absorbed the financial and reputational cost.
The lesson for owners of smaller companies is not that every deal carries a breach of that size. It is that buyers, lenders and their counsel now ask about security as a standard line item. A seller with clean answers moves faster than one who has to improvise.
What buyers examine in a target
Firms that publish diligence checklists describe slightly different lists, but they overlap heavily. One security firm’s guide describes eight domains: external attack surface, breach and incident history, security controls and architecture, identity and access management, data protection and privacy, compliance and regulatory posture, incident response and recovery, and third-party risk.
Here is how those areas translate into requests a seller should expect.
| Area | What the buyer asks to see |
|---|---|
| Governance | Who owns security, written security program, budget and staffing |
| Incident history | Incident records, forensic reports, regulator and customer notifications, any ransom payments |
| Access control | Multi-factor authentication coverage, privileged-account lists |
| Systems and network | Asset inventory, network diagrams, patch reports, endpoint coverage |
| Data | Inventory of sensitive data, where it is stored, whether it is encrypted, privacy notices |
| Vendors | Vendor list, security terms, audit rights, breach-notification duties |
| Resilience | Backup design, restore tests, incident-response and continuity plans |
| Compliance | Certifications, audit reports, insurance, complaints and litigation |
The evidence list above draws on a checklist from corporate counsel and Baker McKenzie. It asks buyers to inventory IT assets, systems, software, websites and applications, to find where data lives and whether it is encrypted, and to identify critical systems. It also points buyers to governance ownership, third-party involvement, outages, written security programs, vulnerability testing, insurance, complaints and litigation.
The minimum data request
At a minimum, a buyer should ask the seller for a description of its data security infrastructure, the categories of personally identifiable information it collects, how that information is used, collected, transferred, stored and shared, and copies of data collection policies where privacy laws apply. That baseline comes from a law firm’s guide to cybersecurity diligence in M&A.
If your company handles customer records, employee data or payment details, assume this list will arrive early. Our own guide to how sellers protect data in a deal covers how to share this material without exposing more than you need to.
Documents versus what is actually running
Policies describe what a company says it does. Testing shows what is deployed. Security practitioners recommend validating critical systems through penetration testing, architecture review and configuration assessment, along with an early outside-in look at public domains, cloud services, web applications and email setup. That same review includes open-source checks for past breaches, regulatory actions, litigation and compromised credentials.

For a seller, this means a buyer can learn a lot without ever logging in to your systems. Run the same outside-in check on yourself first.
The controls buyers look for also overlap with what insurers require. Proving MFA, endpoint detection and tested backups is the same groundwork described in this overview of U.S. cyber insurance requirements, so one round of preparation serves both purposes.
How the process runs and how long it takes
Cybersecurity review usually sits inside confirmatory diligence, after a letter of intent is signed. A common pattern is a 30-to-60-day window before signing, in which the buyer gathers information on security posture, reviews documents, runs interviews, sends questionnaires and follows up on critical risks. KPMG describes this for technology deals, and the sequence applies to most deals.
For mid-market companies, one IT services firm reports that two to four weeks of active work inside that larger window is typical, covering scoping, document review, interviews, validation, reporting and integration planning.
A typical sequence looks like this:
- Scoping. The buyer decides how deep to go based on the target’s industry, data and exposure.
- Request list. Policies, reports, contracts and records are requested through the data room.
- Interviews. The buyer talks to whoever runs IT and security, in-house or outsourced.
- Validation. Outside-in scans and, where allowed, testing or configuration reviews.
- Reporting. Findings are ranked by severity, cost and who is responsible for fixing them.
- Negotiation. Findings feed price, indemnities and closing conditions.
The time pressure matters. Deal teams often have only a short period for technical review, which is enough to read a SOC 2 report but not necessarily enough to confirm the report matches what is in production. A seller whose documents are organized and consistent gives the buyer fewer reasons to ask for more time or a bigger cushion.
The deal process itself also draws attention from attackers, since sensitive information is shared and staff are stretched. Kroll notes this heightened risk around announcement and integration. Controlling who sees what is part of the answer. Our confidentiality ring checklist and the guide to running a confidential sale without leaks show how to stage access.
Legal and regulatory items to review
Cybersecurity diligence is partly a legal exercise. A few U.S. items come up often.
Contract protections
A buyer should include cybersecurity representations and warranties in the purchase agreement. Typical ones say the target complies with applicable data privacy laws, has appropriate privacy policies, and has not received inquiries or faced enforcement actions on data privacy. Sellers should read these representations early and decide, with their attorney, whether they can be given without exceptions.
Vendor contracts matter too. Counsel recommends examining whether vendors owe security obligations, audit rights and breach-notification duties, and considering outside penetration tests or security audits.
Public companies
If the target or the buyer is a public company, SEC Form 8-K Item 1.05 requires disclosure within four business days after the company determines a cybersecurity incident is material. The determination must be made without unreasonable delay after discovery. The rule allows a delay of up to 30 days only if the U.S. Attorney General finds that disclosure poses a substantial risk to national security or public safety.
Government contractors
Companies that hold federal contracts carry additional obligations. A law firm that advises on these deals recommends reviewing policies for safeguarding FCI and CUI, system security plans, plans of action and milestones, incident-response plans, NIST SP 800-171 assessment evidence, SPRS records, CMMC scoping and certificates, and subcontractor flow-down procedures. Its view is that contract commitments can create deal risk even when ordinary commercial diligence looks fine. If this describes you, bring in counsel who knows these rules before you go to market.
How findings affect price and terms
Cyber problems become money problems. Data and cybersecurity risks can increase legal exposure, delay closing and drive post-closing remediation costs. When issues surface, buyers often increase escrow holdbacks, extend survival periods for data-related representations, or require pre-closing disclosure and remediation. An unresolved incident or investigation can also delay signing or closing while the exposure is sized.
The downside is real for buyers who skip the work. Incomplete diligence can lead to significant costs, restrictions on the company or key personnel, a reduced price, closing delays or a collapsed deal. On the seller side, the same findings show up as leverage against you.
Here is how a typical finding moves through a negotiation:
| Finding | Likely buyer response |
|---|---|
| No MFA on admin accounts | Pre-closing fix or price credit for remediation cost |
| Unreported past incident | Larger escrow, longer survival period, specific indemnity |
| End-of-life systems | Price adjustment for replacement and integration cost |
| Missing privacy policies | Closing condition or tailored representation |
| Weak vendor contracts | Request to renegotiate or a specific indemnity |
Security practitioners list the adjustments buyers price in: remediation, compliance, technology debt and security-specific integration costs, such as replacing unsupported systems, adding missing controls, consolidating identity and aligning networks and tools.
After closing, the work continues. Guidance for the first 100 days advises buyers to hold off connecting networks until risks are assessed, inventory all assets and identities, fix critical vulnerabilities first, merge governance and incident response, and review inherited third-party risk.
How sellers prepare before going to market
The best time to deal with this is before the business is listed. Counsel advising sellers says weak attention to privacy and cybersecurity, a data breach, missing privacy agreements or missing technology controls can all affect valuation.
One security advisory firm suggests starting two to four quarters before going to market. Its reasoning is that unresolved findings become negotiating leverage, escrow holdbacks or closing conditions, while gaps you have already corrected can become selling points.
A practical seller checklist:
- Name an owner. Someone, even a part-time or outsourced lead, is accountable for security and can answer buyer questions.
- Write it down. Security policy, incident-response plan, backup and recovery plan, and vendor list.
- Close the obvious gaps. MFA everywhere it matters, patching, endpoint protection, tested restores.
- Map your data. Know what sensitive data you hold, where it lives and who can reach it.
- Collect incident records. Anything that happened, how it was handled and who was notified. Surprises hurt more than the incident itself.
- Review vendor and customer contracts. Check security commitments and notification duties.
- Load it into an organized data room. Our M&A data room checklist for sellers shows where security materials fit alongside financial and legal files.
- Run an outside-in check on yourself. See what a buyer would see from the internet.
Sellers who want to see where cyber readiness fits in the bigger picture can read our guide to pre-LOI diligence for sellers and the piece on navigating diligence without losing leverage.
If you are the buyer
A risk-based approach works best. Not every deal needs the same depth: a company holding health records or payment data deserves more scrutiny than a local service business with a few laptops. Scope the work to the threat level, then ask for evidence tied to each risk. Insist on a remediation list that names the responsible party, the cost and the timeline for each item. Our guide on how to evaluate a business before buying places cyber review next to financial and operational checks.
Our perspective
We have sold over 225 businesses, and we have seen how a late surprise changes a deal. A buyer who finds a security gap in week five does not treat it as a small item. They treat it as a sign that other things may be hidden, and the price or the structure shifts.
That is why we prepare sellers early. Our approach is built on real buyer feedback: we learn what buyers question, then help owners fix those things before they go to market. Cybersecurity is now one of those questions, next to financials, customer concentration and management depth.
Our view is simple. Treat cyber readiness as part of sale preparation, not as a task for the middle of diligence. Owners who document controls, organize evidence and close known gaps give buyers confidence and keep negotiating leverage on their side.
Tucker
Get your business ready for buyer scrutiny
If you plan to sell, start with a clear view of what your business is worth and what buyers will question. Our Free REAL Valuation is a good first step. From there, The Captyx Exit Program helps owners improve the business before the sale, and our M&A advisory and brokerage services cover financial preparation, buyer vetting, diligence support and negotiation through closing.

Buyers can also work with us through Buy-Side Advisory to evaluate targets, including how much diligence a particular deal needs.
FAQ
What is a cybersecurity due diligence checklist?
It is a list of requests and checks a buyer uses to assess a target’s security. It typically covers governance, incident history, access controls, network and endpoint protection, data inventory and privacy, vendors, compliance, backups and insurance. A good one is scaled to the deal’s risk rather than applied the same way to every acquisition.
When does cybersecurity due diligence happen?
Most of it happens after a letter of intent is signed, during confirmatory diligence that often runs 30 to 60 days. Some outside-in checks can start earlier. Sellers who prepare before going to market handle the process with far less stress.
Who should perform it?
Buyers commonly use a mix of deal counsel, internal IT staff and outside security specialists. The legal team reviews contracts, representations and regulatory exposure. Technical specialists validate controls through configuration review and testing. Sellers should have their own attorney and a technical contact ready to respond.
Can cyber findings kill a deal?
They can, though more often they change price or terms. Findings may lead a buyer to ask for pre-closing fixes, a larger escrow, longer survival periods for representations or a lower price. Serious undisclosed incidents can delay closing or end negotiations. Early preparation lowers that risk.
How should a small business owner start?
Name who is responsible for security, write down your policies and recovery plans, turn on multi-factor authentication, and gather incident records and vendor contracts in one place. Then talk to an M&A advisor about how these items fit into your sale timeline.
Sources
- Kroll: Cybersecurity Due Diligence, A Practical Guide
- Saul Ewing: Cybersecurity alert on M&A diligence
- ACC and Baker McKenzie: Buyer Beware, Cyber Diligence in M&A
- BSK: Cybersecurity Due Diligence in M&A Transactions
- CloudSEK: Cybersecurity Due Diligence
- Praetorian: M&A Cybersecurity Due Diligence
- KPMG: Mitigating cyber threats in TMT during M&A
- Corsica Technologies: IT Due Diligence Checklist
- DKBinnovative: Cybersecurity as a Value-Creation Lever
- Skadden: SEC cybersecurity disclosure rules
- Burr & Forman: Cybersecurity Noncompliance as a Deal Risk
- DBL Lawyers: Data and cybersecurity risks in M&A valuation
- St. Louis Bar Journal: The Value of Cybersecurity Due Diligence in Transactions
- ACA Group: Cybersecurity Playbook for the First 100 Days After M&A
- AGDG Law: Cybersecurity traps for the seller and buyer
- Helm Infosec: Cybersecurity Due Diligence for M&A
- U.S. cyber insurance requirements: MFA, EDR and backups






