Last week, a thread in a data governance Slack channel asked, "Did you see the Maersk thing? We just closed an acquisition. What are we missing?" The questions that followed were practical and a bit anxious, highlighting a common issue.
Here's the context. Maersk disclosed unauthorized access and data extraction from a legacy system acquired in a previous deal. An extortion group, WhiteArmor, claimed to hold 100GB of logistics data and demanded $5 million in Bitcoin. Maersk stated the incident was isolated with no impact on other systems. This pattern is familiar to anyone who has inherited infrastructure through a deal. Below are the questions we hear most.
Start with an Inventory
When acquiring a company, begin with an inventory of their systems. You can't protect what you haven't identified. Run data discovery on every inherited environment to determine where personal data is stored, who owns each system, and how they're connected. Ownership often gets muddled during mergers and acquisitions. Assign a named owner to every system. If nobody claims it, that's your first red flag. Under Article 30 GDPR, your records of processing must include these systems. An unrecorded system is both a compliance gap and a blind spot.
Pen Testing Is Essential
Penetration testing isn't overkill before signing a deal; it's essential. It reveals what paperwork can't. During due diligence, penetration tests can uncover weaknesses before you own them. Questionnaires only show what the target believes about its security, while tests reveal the truth. Focus on externally reachable assets, credential hygiene, and paths into the parent network. Findings can influence price, indemnities, and remediation timelines. Article 28(1) GDPR expects you to use processors with sufficient guarantees on Technical and Organisational Measures. Hold acquired entities to the same standard.
Credential Management in Inherited Systems
Inherited systems often come with their own credentials and patch schedules. Review access provisioning and deprovisioning immediately. Look for shared accounts, stale service accounts, and former staff with access. Rotate credentials instead of assuming they're secure. In the WhiteArmor claim, the data allegedly included plaintext passwords. Whether true or not, it highlights attackers' hopes to find poorly stored credentials. Apply policy-based access control where possible, and use tightly scoped roles when necessary. Avoid discretionary access control by default on unfamiliar systems.
Replacing Legacy Systems Isn't Always Necessary
You don't have to replace every legacy system. The goal is to know what you own, understand how systems connect to the business, and ensure controls are effective. Replacement is often slow and unrealistic. If a system must stay, isolate it. Segment the network, restrict API and EDI connections, and log everything crossing the boundary. Test these boundaries regularly. Don't wait for an incident to learn if they hold. Schedule validation regularly and after each integration change.
Breach Notification Timelines
Under Article 33 GDPR, you must notify the supervisory authority within 72 hours of becoming aware of a personal data breach, unless it's unlikely to risk individuals. The UK General Data Protection Regulation has the same rule. Document every incident in your breach register, including ones you decide not to notify, with your reasoning. If the risk to individuals is high, Article 34 requires direct notification to affected people. Data like driver records, phone numbers, and email addresses can trigger this assessment.
Handling Extortion Demands
Deciding whether to pay an extortion group is a legal and executive decision, but you'll need to provide input. Payment doesn't remove notification duties or guarantee Data Purging. You can't verify what the group does with the data afterward. WhiteArmor, which focuses on data-theft extortion, plans to expand into ransomware. A group moving toward ransomware has little reason to honor a deal. Build your response plan in advance. Decide who has authority, who communicates with counsel and insurers, and how you'll assess what data was taken. Treat security as "assumed compromise" and set controls and alerts accordingly. Cycle credentials, tighten access controls, and set up data loss alerts.
Next Steps
For breach handling, read Articles 33 and 34 GDPR alongside your supervisory authority's guidance. For inventory and ownership, the DAMA-DMBOK offers a solid structure for data stewardship across merged estates. For assessing high-risk inherited processing, ISO/IEC 29134 provides a method for privacy impact assessment, and Article 35 GDPR tells you when one is required. If a system falls under high-risk processing and you can't mitigate the risk, prior consultation under Article 36 may apply.
Take the practical step: add an integration security gate to your M&A playbook this quarter. Inventory, test, assign ownership, rotate credentials, segment, and revalidate. Do it before the next deal closes, not after.





