Sicurezza · Strategia · PoliticheAnalisi indipendente · Fonti aperte
Cyber Policy Review
Italiano
EnglishEspañolFrançaisDeutschItalianoPortuguês

Edizione originale in inglese. La traduzione di questa nuova analisi è in preparazione.

Historical case · 2016

Industroyer: When Legitimate Industrial Protocols Become the Attack Surface

Process-aware detection matters when hostile activity resembles ordinary control traffic.

Published: 9 October 2026

In this analysis
  1. What happened and what is established
  2. Why the case changed the discussion
  3. What could reduce exposure today
  4. How the response could be stronger
  5. Policy decision and exercise

What happened and what is established

ESET’s 2017 research described malware capable of interacting with industrial communication protocols and assessed a likely connection to the December 2016 Ukrainian power outage. [1] The later US indictment includes Industroyer among malware used in the alleged campaign. [2] This wording preserves the difference between the researchers’ technical assessment and the government’s subsequent allegations.

Why the case changed the discussion

A protocol can be functioning as designed while its use is malicious. The defender must understand which device is permitted to issue a command, in which state and under which authority. Looking only for malformed traffic or commodity malware misses the management problem: valid operations can be inappropriate for the current process.

What could reduce exposure today

Define permitted engineering paths and changes, reduce unnecessary network reach and maintain an inventory that includes protocol roles. Establish a baseline of expected control activity with engineers. Monitor relevant changes and sequences, not only isolated connections. Passive observation and controlled testing may be preferable to disruptive scanning in sensitive environments; the decision belongs to the system’s operational risk assessment.

How the response could be stronger

Correlate security observations with process state and operator actions. Preserve the evidence needed to distinguish an authorised operation from an unexpected sequence. Validate controller and supporting-system configuration before returning to routine remote control. Restoration should include an assessment of the trustworthiness of the engineering path, not only whether electricity or another service has resumed.

Policy decision and exercise

Ask whether the organisation can explain its most consequential control commands in operational language. Exercise an unusual but technically valid command sequence in a safe test environment. The goal is to verify escalation and authority, not to reproduce a destructive attack on live equipment. A successful outcome demonstrates that cyber detection and engineering judgement can meet in time to protect the process.

References

  1. ESET · Industroyer research · 12 June 2017
  2. 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.

Francisco Javier Jurado Alonso