Maersk recently confirmed a data breach involving a platform from a company it acquired. The ransomware group WhiteArmor claims responsibility, demanding $5 million in bitcoin. They allege they have 100GB of data from the OCF/LF Logistics platform, which was part of Maersk's 2022 acquisition of LF Logistics.
Maersk states the breach is confined to a local system, with no impact on other Maersk systems or those of customers and partners. They report no sensitive data exposure or operational disruption. The investigation continues, but Maersk hasn't disclosed which system was affected, the types of data compromised, or the timing of the breach. This analysis focuses on confirmed details and the attacker's claims.
Timeline
- 2017: Maersk suffers the NotPetya attack, leading to a massive IT rebuild and up to $300 million in damages.
- 2022: Maersk acquires LF Logistics, including the OCF/LF Logistics platform.
- Recent weekend: WhiteArmor lists Maersk on its leak site, demanding $5 million with a 30-day deadline.
- Following days: Maersk confirms the breach, states it's isolated, and plans to notify customers if necessary.
The timeline between the 2022 acquisition and this breach is critical for your team to examine, as the platform remained a separate environment.
Which Controls Failed or Were Missing
Maersk hasn't identified a root cause, but the attacker's claims suggest potential control gaps:
- Plaintext passwords: If credentials were stored unhashed, this indicates a failure in credential storage.
- 33 SUPER_ADMIN accounts: This suggests excessive privileged access and poor administrative rights review.
- Nearly 30,000 driver records and 27,842 mobile device logs: This indicates a large volume of personal data, possibly without proper minimization or retention policies.
- Signed delivery receipts and purchase order data: Business records were accessible from the same environment.
- Data volume: The 100GB data transfer suggests inadequate egress monitoring.
Segmentation appears effective, as Maersk reports no other systems were affected. This isolation limited the breach's impact and is a practice to replicate.
What the Relevant Standards Require
GDPR Article 32 mandates appropriate Technical and Organisational Measures, including pseudonymization and encryption. Plaintext credentials and unchecked privileged accounts conflict with this standard.
GDPR Article 5(1)(c) and 5(1)(e) require data minimization and storage limitation. Large volumes of driver and device logs need a documented purpose and retention period.
GDPR Article 5(1)(f) demands data integrity and confidentiality.
GDPR Article 25 requires data protection by design and by default. An inherited platform must be assessed against your standards.
GDPR Article 33 requires notifying the Supervisory Authority within 72 hours if a breach poses a risk to individuals. Article 34 requires communication to affected individuals if the risk is high. Maersk's conditional notification depends on the investigation's findings. Article 33(5) requires documenting every breach in a Breach Register.
GDPR Article 35 requires a data protection impact assessment for high-risk processing. An acquisition involving large-scale data should trigger reassessment.
GDPR Article 28 applies if the acquired platform processes customer data, as processor obligations continue with the business.
Other regulations may apply, such as the California Consumer Privacy Act and the Personal Information Protection and Electronic Documents Act.
Lessons and Action Items for Your Team
Treat acquired systems as untrusted until proven otherwise. Develop a post-acquisition checklist for asset inventory, data discovery, identity review, and patching. Don't delay securing an acquired platform.
Audit privileged access immediately. Review high-privilege accounts on all inherited systems. Remove unjustified accounts and schedule regular access reviews.
Eliminate plaintext credential storage. Scan for unhashed passwords and secure them with modern algorithms.
Maintain effective segmentation. Keep legacy platforms off shared networks and limit integrations to monitored interfaces like API gateways.
Apply data minimization and retention policies. Conduct data discovery, apply data labeling, and establish a records disposition schedule.
Monitor egress. Set alerts for large outbound data transfers from legacy systems.
Rehearse your communication plan. Prepare a holding statement, customer verification channel, and clear notification rules. Don't claim "no sensitive data disclosed" without evidence.
Plan for extortion, not just encryption. Develop a resilience plan with offline backups and a decision framework for data-theft extortion.
Ask your team: which inherited system hasn't been fully reviewed? Start there.





