Édition originale en anglais. La traduction de cette nouvelle analyse est en préparation.
Historical case · 2017
NotPetya: Destructive Risk Across Interconnected Organisations
A national crisis can become a global recovery problem through ordinary business dependencies.
In this analysis
What happened and what is established
The UK government attributed the destructive June 2017 NotPetya attack to the Russian military. [1] The 2020 US indictment alleges a campaign whose victims included organisations outside Ukraine and describes serious losses across different sectors. [2] These are attributed government assessments and allegations. The analysis does not equate a ransom-like presentation with a dependable recovery mechanism.
Why the case changed the discussion
Our assessment is that shared connectivity, privileged administration and business relationships can turn a local exposure into an enterprise-wide crisis. Resilience requires asking which dependencies could fail together. A geographically separate office may still rely on the same identity, management or recovery services as the site where disruption begins.
What could reduce exposure today
Review trust between business units and suppliers, constrain administrative reach and validate the paths used to distribute software. Maintain recovery copies and administration capabilities outside the ordinary compromise domain. Test whether backup access depends on the very identity environment that may be lost. These controls reduce common-cause failure; they do not guarantee prevention of every destructive campaign.
How the response could be stronger
Prepare for simultaneous loss of workstations, identity and normal communications. Establish restoration priorities with operational leadership and identify clean resources for rebuilding. Keep a defensible record of the order in which services are restored and validated. Logistics, staffing and supplier coordination may determine recovery speed as much as technical repair.
Policy decision and exercise
Ask whether the organisation could rebuild essential identity and management services without trusting the compromised environment. Exercise a regional outage that expands into global shared services. Measure the time to establish clean administration and restore one complete business process, rather than counting recovered machines. The strategic lesson is to limit correlated failure and make enterprise recovery an engineered capability.
References
- UK Government · Attribution of NotPetya · 15 February 2018
- US Department of Justice · Six GRU officers charged · 19 October 2020
Original editorial analysis and paraphrases. Recommendations are distinguished from documented facts; references do not imply institutional endorsement.