When a legacy application stays, which permissions are you actually renewing?

Maersk's acquired-system breach offers a useful distinction without assuming the incident spread. The company confirms data extraction and reports no indication of wider impact. Cybernews reports its spokesperson disputing plaintext-password claims and says the stolen single-use codes were now expired. That does not publicly settle historical redemption or session use.

For a retained integration, the application owner's inventory is only one side. The receiving service needs to confirm which identity it accepts and which operations that identity can perform. A necessary shipment-status read does not, by itself, justify order-creation permission; that is a hypothetical review example, not Maersk's reported architecture.

The article separates historical incident scoping from present-day checks and compares retirement, constrained operation and continued integration.

Sources:

https://www.maersk.com/news/articles/2026/11/11/it-security-incident

https://cybernews.com/security/maersk-confirms-cyberattack-ransomware

Did you learn something new?