Skip to main content
Promotional banner for a CUI buildout guide
Maersk's Legacy Platform Shows Where M&A Risk HidesSecurity & Breach Notification
3 min readFor Data Governance Leads

Maersk's Legacy Platform Shows Where M&A Risk Hides

A legacy platform inherited through acquisition has become the entry point for a reported ransomware extortion attempt against one of the world's largest logistics groups. This incident highlights the risks associated with legacy systems in mergers and acquisitions. Here's what the reported facts reveal and what actions you should consider.

Breach Overview

Maersk confirmed a breach of systems belonging to a company it acquired, with data stolen by the ransomware group WhiteArmor. The group claims to have taken about 100GB from the OCF/LF Logistics platform. Maersk acquired LF Logistics from the Li & Fung Group in 2022. WhiteArmor has demanded $5 million in bitcoin within 30 days.

Maersk states the incident is isolated to a local system, with no impact on other Maersk systems or connected customer and partner systems. The investigation is ongoing. Details about the affected system, compromised data types, or the timing of the intrusion have not been disclosed.

Treat the threat actor's claims as unverified, but use them as a stress test for your own systems. The listed data categories are typical of those in acquired logistics, HR, and fulfillment platforms.

Key Findings

1. Acquisition-Related Vulnerabilities
The compromised system originated from an acquisition and remained accessible years later. The deal closed in 2022, but integration delays can lead to vulnerabilities.

2. Personal Data at Risk
WhiteArmor claims to hold nearly 30,000 driver records, plaintext passwords, mobile device logs, and signed delivery receipts. If verified, this would likely constitute a personal data breach under Article 4(12) GDPR, triggering the notification requirement under Article 33 (72 hours from awareness).

3. Weak Privileged Access Controls
The group claims access to 33 SUPER_ADMIN accounts and plaintext passwords. This suggests common control failures in inherited systems, such as unrotated credentials and inadequate password storage practices, which violate Article 32 requirements.

4. Isolation and Integration Challenges
Maersk's claim of isolation is ideal, but it raises questions about your ability to demonstrate isolation with logs and documentation.

5. Historical Cost Context
Maersk's experience with NotPetya in 2017, which cost up to $300 million, underscores the financial impact of uncontained incidents and the importance of early segmentation decisions.

Implications for Your Team

Acquisitions transfer liability along with assets. Under GDPR, the acquiring entity becomes the controller for the acquired company's processing. You can't use the target's legacy posture as a defense if the system processes personal data in your estate.

Two common failures compound risks: pre-deal diligence often overlooks data protection, and post-deal integration prioritizes revenue systems, leaving legacy platforms unchecked. Ensure your record of processing activities (RoPA) includes all acquired systems.

Action Items by Priority

Immediate Actions (within the current quarter)

  • Inventory Acquired Systems: List each platform, its owner, data categories, user populations, and connections to your core environment. Add each to your RoPA.
  • Audit Privileged Accounts: Remove or rotate dormant administrator accounts, enforce multi-factor authentication, and eliminate plaintext credential storage. Document these actions as evidence of Article 32 compliance.
  • Verify Isolation: Confirm network segmentation, review API and EDI connection scopes, and ensure you can produce logs showing the legacy system's reach.

Next Steps (within two quarters)

  • Integrate Data Protection in Diligence: Request the target's RoPA, breach register, penetration test results, and supervisory authority correspondence. Address gaps as pricing or indemnity points.
  • Set Deadlines for Legacy Platforms: Establish a decommission or migration deadline for each platform, with accountability tied to a named owner and reporting to your DPO.
  • Prepare Breach Playbooks: Define roles for Article 33 notifications and identify affected individuals when records are in unfamiliar formats.

Ongoing Practices

  • Run Early Article 34 Tests: Assess potential high risks to individuals from breaches to prepare communications if needed.
  • Brief Your DPO on Integration Milestones: Ensure the DPO is informed of the acquisition roadmap to avoid surprises.

GDPR official text

Promotional banner highlighting failures found in PCI audits and how to spot the gaps

You Might Also Like