Skip to main content
Promotional banner for the pentest readiness checklist
Acquired a Platform? Pre-Close Audit or Post-Close Fix?Incident Management
4 min readFor Enterprise Sourcing and Procurement Leaders

Acquired a Platform? Pre-Close Audit or Post-Close Fix?

Maersk recently confirmed a breach in a company it acquired in 2022, LF Logistics, where a threat actor stole data from a legacy platform. The ransomware group WhiteArmor is demanding $5 million, claiming to hold about 100 GB of data. Maersk states the incident is isolated to a local system and hasn't affected its other systems or customer integrations.

While details about the breach are still emerging, this situation highlights a critical decision for sourcing and procurement leaders involved in acquisitions.

The Question at Hand

When acquiring a company, how much cybersecurity scrutiny should occur before the deal closes, and how much should be part of the integration plan afterward?

Both sides agree that acquired platforms become your risk. The debate is about where to focus your efforts.

The Case for Front-Loading Security Due Diligence

Advocates for early diligence make three key arguments.

Leverage disappears at signing. Before closing, you can demand architecture diagrams, penetration test reports, privileged-access inventories, and incident history. After closing, you're asking your new subsidiary for favors, and its team may be reluctant to reveal its biggest problems.

Price and terms can absorb what you find. Discovering issues like unmanaged privileged accounts or unsupported components pre-close allows you to adjust the price, set up an escrow, or negotiate specific indemnities. Post-close, these costs become your responsibility. Strong liability terms only help if you know what to protect against.

Legacy platforms hide technical debt. Acquired companies often have systems built for a different security era. In Maersk's case, the threat actor claims the stolen data includes plaintext passwords and 33 SUPER_ADMIN accounts. While unverified, these claims illustrate the kind of weaknesses a technical pre-contractual assessment is meant to catch.

The core point is that you can't fix what you don't know, and pre-close is the best time to ask.

The Case for Deferring Depth to Integration

The opposing view isn't against security but against superficial checks.

Pre-close access is limited. Sellers, under confidentiality and competitive pressure, rarely allow buyers full access to production environments. What you get are questionnaires and curated documents. A SIG Core response shows how a company describes its controls, not whether a forgotten legacy platform still runs them.

Deal timelines are tight. Security teams often have days, not months, and must compete with financial, legal, and regulatory reviews. A rushed review can create false confidence, which is worse than acknowledging a gap.

Real knowledge comes from operating the environment. You learn what a system does by running it: what connects to what, who has access, and which components are neglected. A well-funded, time-boxed integration program with full access can uncover more than a limited pre-close review.

This camp points to containment as the real test. Maersk reports the incident is limited to a local system, suggesting that segmentation between acquired and core environments worked, regardless of what diligence found or missed.

Where Practitioners Actually Land

Most mature teams don't see this as an either/or decision and divide the work based on what each phase can realistically deliver.

Pre-close, focus on high-signal questions. Determine what platforms the target runs, which are end-of-life or unsupported, where data resides, how privileged access is managed, and what incidents have occurred recently. You're not certifying security but identifying deal-breakers and pricing remediation.

Treat integration as a gated process. Acquired platforms should connect to your core environment only after meeting defined criteria. Until then, keep them segmented, with restricted credentials and monitored interfaces. This aligns with ISO 27036 principles: access should match demonstrated assurance, not contractual status.

Classify acquired systems like any other dependency. Apply your Criticality Classification to the acquired systems immediately. A legacy fulfillment platform with sensitive data deserves the scrutiny of a high-tier vendor.

Set a remediation clock. Agree before closing on how quickly acquired systems must meet your baseline: credential hygiene, multifactor authentication on privileged accounts, logging, and patch currency. Without a deadline, legacy exceptions become permanent.

Pre-plan the Vendor Breach Management playbook for your subsidiaries. Maersk's guidance to customers to verify unexpected communications through known contacts is a sound template. Your acquired entities need the same incident escalation path and communication plan before issues arise.

Our Take

Front-load the questions, but be realistic about what pre-close diligence can prove. It's effective at finding deal-breakers and setting terms but not at proving the absence of weaknesses. Treat a clean pre-close review as a starting hypothesis, not a clearance.

The real risk isn't skipping diligence or doing it superficially. It's treating the close as the finish line. A legacy system that enters your environment without a remediation deadline, segmentation boundary, and named owner becomes a liability.

If you're a sourcing or procurement leader involved in M&A, push for three things: a technical security gate in the deal timeline with authority to adjust terms, a segmentation-first integration standard, and written remediation deadlines tied to access into your core systems. Maersk's reported containment is a reminder of why the second one matters most. Diligence reduces surprises; architecture limits what those surprises can affect.

Promotional banner graphic asking if you are ready for PCI DSS 4.0 with a call-to-action to get the guide

You Might Also Like