Balancing on the rail – considering responsibility and restraint in the July 2021 Iran railways incident

JD Work [1], [2]

An intrusion against a railway network, resulting in destructive effects leading to disruption of cargo and passenger transportation, would in previous decades likely have been considered a major strategic attack. Early writings on cyber warfare posited such actions only in theory, within the context of adapting ideas of other long-range strike and sabotage operations to the access opportunities afforded in a new operating environment.[3] Yet an incident in Iran that surfaced in July 2021 has passed with only relatively limited attention, having been all too easily overlooked in the surge of recent ransomware incidents and the other immediate fires that command current intelligence production priorities and readership. Nonetheless, the case deserves greater scrutiny – as much for what was not done, as for what transpired on the wire. While superficially shocking, as an action against critical infrastructure with civil dependencies, it is nonetheless likely a rare example of responsibility and restraint in the employment of offensive cyber operations for covert action objectives.

This article will consider the operational details of the intrusion incident and its context as part of a wider campaign leveraging related malware variants against similar regional targets. We will examine the decision to target the railway network from the normative framework supplied by the Tallinn Manual. Recognizing that customary international law does not easily address the case at hand due to involvement of apparent non-state actors outside of acknowledged conflict, we will proceed to consider the operational-level decisions made in the planning and execution of this intrusion and its effects delivery, identifying factors of cyberweapons design, controlled employment, and available effects options not pursued by the unattributed attackers that in total demonstrate due care and responsibility. We will close with a look at the wider regional context contemporary to these events, and the implications for both current and future responsible offensive cyber operations.

Intrusion and actions on objective

Between 9-10 July 2021, destructive termination of an existing intrusion resulted in the disruption of train services in Iran. While initial reports from local media suggested extensive cancellations and delays to scheduled movement of rolling stock, including passenger routes, the Iranian Transportation Ministry attempted to deny that any disruption had taken place. Handheld imagery then surfaced which showed cancellations listed on public display monitors at the Tehran central rail station at Rah Ahan Square, alongside a message directing complaints to a phone number. This number was found to be the public line for the Office of the Supreme Leader (Beit-e Rahbari). Additional impacts to the Iranian Ministry of Roads and Urban Development public website were also reported on 10 July.[4]

An Iranian cyberdefense firm which supplies the country’s national antivirus software provided the first public reporting on the malware payload used to deliver these effects. The payload was initially called Breakwin, and was described as a wiper also capable of corrupting master boot record hard disk partitions.[5] It is likely that the firm was able to acquire these samples through either antivirus telemetry (although such telemetry was degraded by the extent to which the unattributed operators were able to disable endpoint protection), or through the firm’s sandbox services (which provide other Iranian researchers with a detonation and automated behavioral analysis environment), rather than directly through digital forensics/incident response (DFIR) and associated recovery efforts at the targeted Iranian networks. Direct DFIR engagement findings would presumably have been handled in a nonpublic manner. The company is known to provide additional malware analysis services to the government of Iran, but these are generally conducted under nondisclosure restrictions. Given the Iranian government’s sensitivity to the incident and earlier cases, it is unclear why the firm chose to disclose technical details which contradicted official narratives. This suggests disconnects between line malware intelligence efforts and ministry security structures. It is also not known why recovered samples were uploaded to public malware repositories outside of Iran.

While no samples were identified by the Iranian researchers, the description of the malware was sufficient to allow at least two separate Western firms to acquire and reverse engineer the payloads, along with additional related components. The latter payload elements were possibly not previously identified by the Iranian analysts, likely due to limitations of their detection, telemetry processing, or analytic tooling. Alternatively, if known to Iranian defenders, these elements may deliberately not have been disclosed. (Reasons for such nondisclosure may be complex, from compliance with regime attempts to control embarrassing or sensitive information, efforts to distinguish privately circulated reporting offering additional detail for subscription consumers, or even incomplete technical analysis).

Initial intrusion reportedly took place as much as one month before effects were delivered.[6] The destructive payload – dubbed Meteor by the malware’s designers – appears to have been developed at least six months earlier, and was staged at an unknown time prior to execution after initial intrusion. The payload consisted of multiple components triggered based on automated scripts, with pre-configured execution parameters. Final destructive termination was initiated based on a time trigger, and rendered infected systems unusable through a sequence of commands to disconnect individual machines from enterprise networks, defeat endpoint protection features, erase local logs, lock out local users, overwrite files on targeted systems, corrupt the master boot record, and display a screen locked image crafted by attackers (which was the source of the message seen displayed at the Tehran station). [7]

While technical analysis of recovered malware provided strong insights into the intrusion incident and its destructive termination, it must be acknowledged that this intelligence picture remains incomplete. It is not known how the effects payloads were delivered to the target environment, nor what other actions may have been executed against network infrastructure including routers, enterprise orchestration and management services, or other systems. It is however clear that there was no apparent impact to operational technology (OT) network segments in any reported descriptions of the event.

A previously unknown self-styled hacktivist group calling itself “Predatory Sparrow” (گنجشک درنده) claimed responsibility for the attack on 9 July 2019, citing Iranian state Fars news agency reporting and stating that they sought to protest abuse of the nation by its government.[8] The group apparently took its name from the Passer montanus tree sparrow with habitat in Iran, and its logo incorporates a cartoon bird in the style of the popular “Angry Birds” game franchise against a digital circuit background. The use of bird naming conventions is common within the Iranian hacking scene, with earlier groups such as Parastoo (“Swallow”) having used similar monikers.[9] Major attack campaigns attributed to the Iranian government, such as Ababil, have also referenced the theme.[10] The Predatory Sparrow claim received almost no attention at the time, although it was immediately challenged by an Iranian actor demanding “proof of exploit”. No response was noted in public social media, although further unknown private communication through the Telegram app may have occurred on a channel provided by the Predatory Sparrow group.

Predatory Sparrow logo

The campaign in context

The Meteor code was found to share a high degree of similarity to other malware variants that may be evaluated as part of the same family, and which industry has assessed as evolving generations of tooling over time. These earlier payloads, Comet and Stardust, have been in use since at least September 2019.Previous recovered samplesdid include configuration elements providing victimology information, including indications of use against targets in Syria. Attacks against these networks, the Arfada Petrolum and its parent Katerji Group companies, involved unique images displayed on destroyed victim computers that claimed responsibility in the name of a self-styled hacktivist group calling itself Indra. This name is also found as a string in earlier malware artifacts. The group has been publicly claiming responsibility for cyber attacks against the Syrian regime since first announcing an attack on another Syrian firm, Alfadelex, in September 2019. Indra has also claimed additional unconfirmed intrusions against the airline Cham Wings and the Banias oil refinery.[11] In the latter case, the group provided imagery of a purported industrial control system human machine interface display, depicting crude oil and fuel oil flow, electrical systems status, and emergency stop controls.

The Katerji Group is a primary supporter of the Syrian regime. Its founder, Hossam Katerji has been a member of the Syrian Parliament since 2016, and along with his brothers has been a key financier involved in oil, construction, agriculture, and other commodities transactions. The firm’s assets were estimated at over USD600 million in 2019.[12] The group also reportedly controls multiple militias throughout the country to protect and advance their commercial interests, and are allegedly closely aligned with Iran.[13] The firm has also been accused of facilitating transactions with Daesh.[14]

Indra accounts further claimed that the Cham Wings intrusion provided intelligence on the movements of senior Iranian Revolutionary Guards Corps (IRGC) general Qassim Soleimani, which identified an alleged alias used by Soleimani for travel between Iran, Syria, and Iraq. Exfiltrated “sensitive documentation” was said to have included travel records one day before he was killed in a targeted US airstrike near Baghdad International Airport in January 2020. Indra claims the hack revealed “the stupidity of the former Quds Force commander” in using obviously false passport and other reservation data, and that this led directly to Soleimani’s targeting and death.[15] This is the first public allegation of cyber operations involvement in the strike. However, this claim cannot be independently evaluated based upon open-source information.

The Indra group apparently ceased further public claims as of November 2020. The gap between this halt in activity, and the Comet/Stardust code family resurfacing with the new Meteor variant in July 2021, allegedly in the hands of a separate hacktivist group opposed to the regime, creates substantial uncertainty as to the actual relationships between these entities.

The author here deliberately does not reach attribution on this case. Multiple hypotheses have been raised in industry reporting and in debates within private trust groups, none of which have resulted in definitive analytic conclusions. Neither is it at all apparent that this campaign has concluded, despite the apparent current cessation of activities by the hacktivist entities who claimed responsibility.

Normative problems

Despite decades of acknowledged military and intelligence planning that has treated cyberspace as a potential domain for conflict, there remains few case examples through which to explore operational behavior – especially under crisis pressures. The vast majority of these cases to date merely highlight the problematic employment of offensive capabilities in immature concepts of operation, using portfolios that were clearly untested in controlled, target relevant range environments, and that lacked appropriate management control and oversight by higher echelons. This is unsurprising, where major incidents emerged from authoritarian states that apparently remain largely unconcerned by the hitherto weak reactions of Western states to ever more egregious campaigns across critical infrastructure networks. As additional states, and other players in the global competitive space of the cyber domain, develop their own offensive cyber operations capabilities, it has become increasingly important to understand how this instrument ought to be used – and not merely how it has been abused in the past by malicious actors. Mature planning, accounting for the complex competing equities and potential harms in a tightly coupled global domain is a substantial burden even when considering operations intended for intelligence objectives, or as active defense response options. Offensive cyber operations involving effects on objective with disruptive or destructive intent face a still higher bar of responsibility.

Normative aspirations have sought to impose restraint in the selection of classes of targets that may be engaged. Yet despite substantive international attention and diplomatic engagement in both government and private channels, these efforts have had little practical effect. It is unfortunately unrealistic to expect that calls for placing all critical infrastructure targets out of bounds will be heeded by global adversaries, nor that even the most well intentioned of states will be able to completely exclude the entirety of a target state’s strategic networks from the calculus of politics pursued through other means. But even as the hopes of formal normative agreements continue to falter in the face of realpolitik, the prospect of more responsible decisions taken at the planner and operator level – and reinforced through management and oversight – are more important than ever. It is through these mechanisms we may hope to see a form of convergence towards agreement around behaviors that are more responsible, or at least less potentially destabilizing. Tacit bargaining through repeated interactions, resulting in boundaries of agreed competition, is one of the core pillars postulated in cyber persistence theory.[16]

Targeting

It is impossible to consider this case without addressing the matter of target selection. As a general rule, it is better that critical infrastructure upon which civilian populations depend should not be subject to attack, as an extension on the prohibitions against attacks on civilian populations.[17] Yet neither should a state presume that they will be able to count on such principles to stay the hand of rivals in the face of other belligerence. It has long been considered permissible to target even civilian objects (such as critical infrastructure networks) where “by their nature, location, purpose or use make an effective contribution to military action”, and “whose total or partial destruction, … or neutralization offers a definite military advantage”.[18]

Conflict status and belligerents

There are substantial gray areas in considering the application of this principle to the Tehran incident. No state of formal military hostilities existed between belligerents in this case, and therefore most international humanitarian law rules that control targeting are not applicable here. However, it has been argued that customary international law factors ought to be extended as a matter of normative principle to encompass actions in otherwise undeclared engagements, outside of armed conflict. Such arguments for expanded application of these principles rest upon the idea that the intent in drafting the original foundational instruments of the Hague Convention, Geneva Convention, Rome Statute, and associated treaty mechanisms is a vital component of international order, and that it is appropriate and necessary to conform to this intent in new situations that could not have been envisioned by the original drafters. (The opposing argument should also be noted: that the original agreements were important in outlining both prohibited conduct, but also delineating areas of state power that the involved parties chose deliberately to exclude from restrictions, as a limit to abstract ideals.)

Further complicating this analysis, one party at least represents itself as a non-state actor. While considerations of combatant status also have no application during peacetime, it has also been argued that these ought be normative considerations in offensive operations. As such, if claims of responsibility are taken at face value, the offensive actor here would appear to be an unprivileged belligerent, not entitled to combatant immunity.[19] Unprivileged belligerents are generally assumed in most analysis to be presumptively improper in the normative sense, although this is a view that is grounded in and seeks to reinforce the state’s monopoly on legitimate uses of violence – in practice quite often challenged by the facts on the ground of force generation and employment in contemporary conflict. Nonetheless, cyber operations by non-state actors are generally considered not to breach standards of customary international law, such as being considered as a use of force, a prohibited intervention, or violation of sovereignty, given that these standards apply to states alone.[20] It must also be noted that the notion of an unprivileged belligerent has been in some legal analysis supplanted by a focus on direct participation in hostilities as determinant of combatant status.[21]

However, it is also unclear if a de facto relationship between the irregular actors and a state that might be considered to be a party in wider regional conflict may be present, which might change such analysis upon more comprehensive consideration.[22] Given that at least one potential attribution hypothesis has been debated which encompasses contractor operations, and furthermore a plausible interpretation of the contractor as essentially mercenary in character, additional complications arise. If this theory is given weight, then such mercenaries involved in cyber operations would also be considered unprivileged belligerents.[23] Yet even otherwise organized armed groups, properly under military command and meeting other combatant criteria, are considered unprivileged combatants if they fail to conduct operations in accordance with the laws of armed conflict. Which returns us to the core issue over the propriety of target selection.

Target of military use and advantage

While transport networks here were almost certainly entangled with civilian uses, targeting is generally not restricted only to objects in immediate military use. The precise contours of the nexus with military activities, scoped by duration of current or future military use, direct or sustaining contributions to warfighting functions, absolute or relative value of contribution and therefore associated military advantage accrued by neutralization, and associated factors renders this a complex matter.[24] The state-owned nature of both the rail infrastructure in question, as well as its supporting information and communications technology services, and the predominant role of the IRGC-associated structure of bonyad enterprises (charitable trusts that play a substantial role in the Iranian economy), also introduces additional complications of military location.

The manner in which these networks were provisioned, and made distinct from IRGC and its state enterprises is salient to this analysis, but deeply unclear from the perspective of outside observers. IRGC-owned and -controlled enterprises encompass a number of entities involved in railway transport.[25] A number of these are sanctions-designated entities due to their use in illicit proliferation related activities – including among others the Bonyad Eastern Railway Company, the Sina Rail Pars Company, and the Kaveh Pars Mining Industries Development Company’s subsidiary Tehran International Transport Company, which are part of the Bonyad Mostafazan foundation designated by the US government under Executive Order 13876.[26]

If the unattributed operators acquired their unknown access to the target through a known military network, and delivered effects accordingly, this may well be considered a valid military location by logical address space, even if distinct in physical geography – especially where specific network geolocation may not have as readily been ascertained by the offensive operators. Designation under international sanctions would suggest sustained military use sufficient to overcome simple presumption of civilian character, even as the infrastructure also continues to be used for civilian purposes. Indeed, Tallinn discussions explicitly encompass this, listing “civilian rail networks being used by the military” as a target liable to attack under otherwise appropriate circumstances.[27]

Cyberweapons effect and review

Targeting is inextricably bound to intended effect. Importantly, while the observed destructive intrusion impacted data upon which the functionality of physical rail operations depended, resulting in disruptive consequences for civilian activities for a period, this clearly did not reach the level of damage to those physical objects, injury to civilians, or loss of life. The action is therefore almost certainly de minimis when considered in current interpretations of customary international law, and arguably does not constitute an attack by these standards.[28]

Critically, the events in this case suggest that greater potential impact rising to a different threshold may have indeed been possible, given the extent of access to the target network apparent in the operation, but that the unattributed operators chose deliberately to employ effects that would avoid such outcomes. This strongly distinguishes the present case from earlier incidents such as the NotPetya/Nyeta wiper operations, in which extensive collateral damage to transportation targets occurred as a result of unconstrained wormable propagation of destructive payloads and where adversary operators made no effort to impose guardrails on effects against additional indiscriminately impacted targets they had not characterized or even identified a priori.[29]

Apparent restraint also distinguishes from other cases that may be theorized in which an attacker might have wished to achieve more substantive physical effects, but did not reach this threshold due to capabilities limitations or operational failures. No such factors were evident in the Tehran case. To the contrary, deployed payloads explicitly specified deletion targets with multiple validation controls. This is strongly characteristic of a deliberately engineered weapon that has been designed with more than passing considerations of legal review.[30]

It is important, for the purpose of this analysis, to note that the ostensible purpose of the attack, as declared by unattributed operator messaging in the event, is not necessarily the actual objective sought in the action. The highly public face of the operation, as part of an event that planners and operators may have anticipated would receive global attention based on prior media coverage of other events involving Iranian networks, may not present the controlling reasoning of advantage obtained by denying, degrading, or destroying this target. Public messaging may have been complementary to, or even independent of, the functional advantage.

Intangible exclusions, reversibility, and morale considerations

International legal experts have for some time also explicitly argued that data on target systems and networks are excluded from the definition of an object for the purposes of evaluating damage, hitherto having referred solely to tangible and physical things in ordinary meaning. This matter has remained in dispute, with the degree of centrality of specific data (alone, in or larger aggregate) to civilian populations emerging as a key factor in weighing harms.[31] As the importance of virtual objects to the functioning of modern economies grows, it has been argued that this exclusion does not properly take into account the impact on civilian populations.[32] However, to date any such expansion of the rule has not been generally accepted, as much as it remains a normative aspiration.

The question of data as a targeted object also becomes further salient when considering reversible effects, both in terms of international law and international relations.[33] Considerations of damage must be evaluated very differently when assessing temporary disruption from permanent destruction. In the Tehran incident, effects were delivered in a manner that indicated awareness of the backup solution used by the target. While it appears from observed payload configurations that wiping effects were also directed against these backups, it is unclear if this was executed broadly across all backup instances on the network or if the unattributed operators preserved selected backups that would enable reconstitution at delay. Multiple configuration examples have been reported from the attack, with backup nodes not specified as targets in some instances.[34] This is further complicated in that backup solutions appear to have leveraged software provided by a US-headquartered firm, transactions which are presumably prohibited under current sanctions. However, Iranian IT engineers employed in sanctioned enterprises – including the state-owned oil company – have frequently listed experience with this solution, and earlier generation versions of the software were observed in underground software distribution through at least March 2021. Actions against targets acquired in violation of sanctions restrictions take on a different character than other mere civilian objects.[35]

Impact to civil populations must also be weighed based on the degree of dependence on denied and degraded systems. Iranian passenger transport has adopted modern payment and ticketing systems only recently, and manual fallback options for recovery remain. In this case, no indications of deliberate targeting of point of sale infrastructure or other systems associated with these functions were observed (although these may have been degraded by generalized effects across the network). While less convenient, the railway could resume transportation services using prior manual ticketing processes as an interim measure, further arguing that civil impact was minimized. This is less true of military and proliferation related use of rail services, which involve more complex problems of tracking shipping containers, bills of lading describing contents, and the details of intended cargo destinations – which as shell companies or other front entities may exist almost nowhere outside of these databases.

The de minimis nature of any physical effects in this case, within the law of armed conflict, also rules out violations of the prohibition on cyber attacks intended to spread terror among the civilian population. Indeed, Tallinn discussions explicitly envisioned potential offensive operations against mass transit, but within the context of causing fear of loss of life or injury. [36] In contrast, disruption in the extant case was explicitly accompanied by messaging which indicated no further escalation of the event. Rather, the focus of communications by unattributed operators was on highlighting otherwise repressed political tensions undermining the Iranian regime, distinct from statements against the population as a whole. These are characteristic of messaging one would see in psychological operations campaigns with intended effects directed against leadership legitimacy. International legal consensus has explicitly declared such psychological cyber operations do not qualify as attacks.[37] Further, even if such messaging, tied to the disruptive or destructive event, was to result incidentally in the decline of civilian morale, this would not be considered collateral damage.[38]

Other considerations

One may also view the intrusion and effects delivery in Tehran not through the lens of military activity, but as covert action. This line of thinking is somewhat unique to the United States’ views, as the label is not recognized outside of US domestic statutes. International law is generally silent on such matters, much as in other activities closely associated with espionage. Yet even states with strong commitments to international order have occasion to resort to unilateral action due to structural weaknesses of the global system. While some have asserted such actions are presumptively illegitimate, a more robust debate will consider the circumstances, intentions, and employment.[39] However, consensus on application of international law has been slow to develop due to the reluctance of states to acknowledge and defend practices, even at later remove.[40] Yet there remains a need to understand actions which arise from contexts treated as espionage in customary international law, but that approach possible threshold of attack – whether the kinetic bright line of human casualties, or the long shadows of destructive effects.

In light of what remains significant unresolved disagreement when considering application of abstract normative principles to actions on the wire, which are all too commonly encountered when attempting to contort the body of customary international law to consider novel actions in the cyber domain, we must turn instead to the questions of operational conduct. It matters as much or more at present, where law is silent (or unable to coherently speak), that the planning and execution of offensive cyber effects operations is responsible.

Observed indications of responsibility and restraint

If as Lawrence Lessig has stated, “code is law”, then developers and operators are now responsible for decisions that previously would have been reserved for policymakers and other elements of the sovereign state.[41] This is a practical devolution of functional authority that places on those conducting offensive cyber operations a burden to “do right” even as they may pursue their competitive interests against other states and non-state targets. Black letter law and formal policy always lags the realities on the ground, especially in fast-moving technology spaces. The weight of these responsibilities requires us to critically examine new cases not just in abstract legal frameworks but in operational detail. Where legal and norms-oriented approaches have not yet gained traction, we may yet see functional practices and de facto standards for a more professional kind of offensive behavior emerge from ongoing interactions on the wire.

The longstanding over-classification of even the most basic concepts of offensive cyber operations has for decades limited discussion of what could, and indeed should, be fundamental principles for the conduct of intelligence and covert action executed through malicious modification of systems and networks. This has led to ad hoc experimentation in which hostile operators frequently accomplish some intended objectives, but often with serious consequences to uninvolved third parties. These failure modes are generally well highlighted in current cyber threat intelligence. However, it is also important to note features which display a greater degree of responsibility.

Sadly, in recent cases of adversary action such as the HOLIDAY BEAR/DARK HALO/STELLAR PARTICLE/NOBELLIUM intrusion, at most one can note that adversary behavior was less irresponsible than in prior campaigns such as those conducted by earlier Russian intelligence service attributed operations by SANDWORM/VOODOO BEAR/IRON VIKING, or Chinese intelligence service attributed operations by HAFNIUM and follow-on activities across associated intrusion sets.[42]

Responsibility in offensive cyber operations is not merely the result of good intentions. Rather, it requires deliberate planning, engineering, operational, management, and oversight efforts throughout the lifecycle of a campaign to ensure that access and actions on objective are properly aligned, adequately tailored, and appropriately balance potential harms to competing equities whilst accomplishing mission objectives. Responsible conduct requires programmatic maturity, individual professionalism, and organizational focus to achieve. Given that responsible offensive cyber operations are carried out through more than mere intention, characteristic features of these behaviors may be seen in the artifacts of specific engagements. Further inferences may also be drawn from these observables.

Tailoring

The incident in Tehran is notable in that it suggests that offensive capabilities were well tailored, through substantial intelligence support including extensive reconnaissance within target networks. This likely allowed for deliberate selection of specific nodes for attack effects. This is significant, in that the unattributed operators appear to have deliberately refrained from any effects delivered against the railway operational technology network segments.

While substantial unknowns persist regarding the manner in which target reconnaissance was executed, the operators took due care to ensure that whatever access options and tooling were employed for this phase of the action remained distinct from the payloads which delivered destructive effects. This is critical towards ensuring distinguishability across campaigns and in future operations, where intrusions executed for intelligence objectives are otherwise difficult to tell apart from effects operations.[43] Such distinguishability is important to preventing potential inadvertent escalation or other negative outcomes from adversary misinterpretation of incompletely observed intrusion.

Tested capabilities

It is further important that the payloads appear to suggest substantial quality assurance engineering. Multiple measures to ensure redundancy of key guardrail functions seem to have been deliberately introduced, and the developers apparently sought to provide continuing state of health status so that operators would have positive control throughout delivery and execution. These capabilities have hallmarks of prior operational test and evaluation, likely within controlled range detonation of environments. This remains a substantial requirement of maturity when engineering new offensive capabilities portfolios.[44] The evolution of the malware family across prior incidents also suggests the live fire assessment was incorporated into a continuing review of the tooling and its performance.

Test and evaluation efforts were however not entirely perfect. Technical analysis suggests a seam between capabilities developers and operators’ implementation, indicating that a complete end-to-end package of payload and offensive deployment scripts were not assembled as a cohesive whole until engagement. This is consistent with programmatic maturity, but within an operations model that relies upon modular options composed at point of need. In this case, such a seam did not appear to compromise responsibility for discrimination and restraint – rather it merely resulted in what some would characterize as operational security lapses. In the hands of other operators, or under different targeting circumstances, such disconnects between different functional roles might however have turned out differently.

Constrained automation

While the deployment of the Meteor destructive payload and its associated components was highly scripted, this automation did not permit indiscriminate autonomous behavior. The detailed automation features specified, to a high degree of control, elements of the target to be serviced for effects and did not allow for non-specified elements to be struck. This included as an early step the deliberate isolation of specific endpoints from the wider network environment.

Critically, the payload did not contain logic to independently select new targets, nor to further propagate through the network to deliver further effects. Such autonomous additional targeting is not presumptively irresponsible, but must be appropriately constrained within carefully defined parameters of action. This requires that formal principles of target discrimination, in both the technical and legal senses of the term, be incorporated into command-and-control functionality. It is also best if such capabilities require a human on the loop, if not directly involved in issuing commands to execute against independently discovered targets. In the current case, the extensive reconnaissance prior to execution appears to have precluded the need to conduct further reconnaissance by fire through automated actions.

Paths not taken

Given apparent extensive prior access to the target, a variety of effects scenarios highly likely could have manifest within the rail network, but did not. There are no indications of destructive or disruptive effects against operational technology networks. This does not appear to have been a result of capabilities limitations, but rather deliberate decisions not to pursue available options. Indeed, code features observed to be present would have enabled additional effects with trivial effort. The Meteor wiper supported specific designation of processes to kill, although none were so specified in observed deployment. This function could have readily incorporated even publicly known process kill lists from other malware deployed against industrial control system environments, such as the EKANS/Snakehose ransomware variant (itself leveraging iterated development from the MegaCortex malware). [45] These static lists, while not tailored to the Iranian rail network, likely would encompass at least some functionality expected to be encountered in the operational technology segment of the target environment. Given the extensive reconnaissance on target, it would have likewise been a relatively simple processing and exploitation task to compile a more narrowly tailored process kill list specific to the network as configured.

Additionally, the presumed level of access demonstrated by the operators in this case would likely have served to provide options against unique features of the railway target using non-public capabilities that could be developed based on descriptions of other classes of known vulnerabilities previously identified in similar targets. Automated signaling and switching technologies with network connectivity would be natural targets should an attacker wish to cause more extensive impact to physical plant. Disruption of these functions could create effects including setting conditions to foul track routing in a manner requiring extensive manual effort to reset, or even create enhanced risks for collision of rolling stock.

The current Iran railways signaling system is reportedly built largely upon a legacy, analog frequency modulated (FM) radio network connecting to a digitally switched network management terminal. This dedicated system provides railway dispatch and command functions, as well as supporting additional public security communications. The dedicated network is reported to be connected to a TCP/IP network.[46] New automated signaling functions, including GSM-R network options, have been variously pursued, to increase rail transit capacity and as part of regional interoperability efforts.[47] These functions almost certainly offer vulnerabilities that could have been exploited by a sufficiently skilled attacker. Prior industry research has demonstrated widespread vulnerability discovery in rail signaling functions, including options to deliver to denial of service effects with potential safety critical impacts.[48] Indeed, Iranian researchers have also previously focused on analysis on signaling failures as part of modernization investments.[49]

It is unlikely however that defensive research efforts have fully remediated potential exploitation opportunities, especially given extended access to the target network demonstrated by the unattributed operators in the current case. As a result, it is even more notable that no such effects appear to have been scoped or otherwise pursued in the July 2021 intrusion incident.

Nonproliferation considerations

Interestingly, these tools appear to have been deliberately designed to incorporate only well known, extensively documented features that have been previously seen in the wild in other malware families. This is an additional hallmark of responsible operations, in which more sophisticated planners will consider the potential proliferation implications of deploying code which may both be directly repurposed if recovered from a target system or network, as well as the potential knowledge transfer to both the immediate adversary based on weapons technical intelligence derived from reverse engineering and behavioral analysis of observed implants. (The latter type of proliferation is also of concern for all other possible observers that may have collected against the event, or acquired samples through subsequent circulation among cybersecurity research communities.)

The primary effects mechanisms of the Meteor wiper include deletion functions that have been compared directly to the NotPetya/Nyeta malware. While this is likely somewhat of an overstatement, the overall structure and logic of the tooling is exceptionally similar to many other contemporary ransomware variants, including publicly circulated open-source tooling used for threat emulation and other red team engagements. Additional functionality is provided from abused administrative software in circulation in the underground market since at least 2006. These design characteristics will have taught nothing new to any observers. Additional commands are executed through native system utilities in a manner that would be familiar to the penetration testing community of practice.

The selection of a time-based effects trigger is also significant, although frequently overlooked. While there are other more subtle options, which may correspond to additional operational objectives, the choice to employ a literally decades old design, previously seen in countless other incidents in the wild, provides additional assurance against proliferating novel concepts of operation.[50]

Towards auditable implants

The Meteor payload and its associated automated scripting may be seen from one perspective to have suffered from multiple operational security failures, had the unattributed developers and operators been focused exclusively on non-detection. In particular, Powershell commands intended to protect deployment of malware components through manipulation of endpoint whitelisting provided transparency into installed malicious tooling. This was leveraged in subsequent technical analysis of the malware. Some of the identified malware samples in the campaign were also found to have retained strings used by developers for debugging purposes, which are more commonly eliminated when deployed for operational use. Much of the configuration of the tooling was also left in readily understood English, whereas malware developers under more routine detection pressures will seek to obfuscate functionality in more elaborate ways. Critically, the implant also incorporated functionality not used in the extant attack, which could have been removed by an actor more focused on denying potential observables about future capabilities options.

However, these choices may also be considered as possible decisions to ensure that the attack was not misinterpreted by observers, and that analysis of any recovered samples of this specific weaponized code instance could be completed quickly in order to reduce potential tensions that may arise from uncertainty around the further extent of immediate action. While planners and developers that build tooling for long-term espionage-focused campaigns may choose to prioritize non-detection features, when considering execution of deliberate effects operations additional factors of target (and importantly, target leadership) reactions must be considered.[51] These decisions are relatively costly for planners, in that they trade off features that may otherwise maximize probability of mission success in an attempt to introduce elements that may reduce chances of hostile cyber intelligence services failing to accurately observe and understand an action. These decisions also presume interactions over a relatively shorter timespan, where the cumulative effect of such options may compound costs for the responsible operator in extended competitive and conflict iterations.

Ultimately, such choices lead to a potential scenario in which an attacker may choose to deploy what are effectively auditable implants. At the simplest level, these artifacts may include specific watermarks intended to convey intended function, even voluntary attribution.[52] More complex tooling in this model documents within itself its scope, the actions it has taken, and importantly serves to rule out other actions not taken. The expectation is that such auditable features may be obfuscated, or perhaps even fully encrypted – to enable an operationally relevant window of time for mission completion, after which it is assumed that a sufficiently skilled technical intelligence team will be able to reverse engineer the artifacts and reconstruct the relevant events of the effects operation. This may even be further enabled by post hoc release of decryption keys for such audit artifacts, either as part of termination and withdrawal from access footholds, or through other channels. While it does not appear that the Meteor implant was designed deliberately to offer such post-incident features, many aspects of the supposed operational security mistakes do serve to offer similar utility for analysis after the fact.

Implications and outlook

This case is an important window into contemporary cyber operations praxis, and a rare example of more responsible operational planning and decisionmaking than is typically seen in the largely unrestrained and ever more escalatory actions of authoritarian and revisionist states that dominate current intelligence reporting and media headlines. However, it is also ethically challenging on one level, in that it remains unattributed – given that claims of responsibility by the identified hacktivist actors must necessarily remain suspect. Indeed, this uncertainty of attribution when coupled with cui bono analysis, has reportedly stayed the hand of some industry researchers who might otherwise have provided additional technical review.[53] In one sense, this is understandable in that observed victimology to date suggests that the Western customers of major cybersecurity firms appear to have little reason to be concerned about this threat activity. The tooling itself poses little proliferation risk. From this perspective, it is perhaps right and proper that the incident be set aside, to allow resources to be focused on the ever continuing press of other new samples and fresh intrusions. Such a decision also does not trigger the ethical implications inherent in providing public analysis of malware development and operational tradecraft which may be abused by adversary actors to improve detection and engineer new countermeasures.[54]

There is nonetheless a balance of competing harms. The near-exclusive focus on what is entirely irresponsible behavior by a series of adversaries means there is little to no discussion of what intrusion activity “done right” looks like. This is even more true of effects operations. This leaves academics, policy communities, and even developing programs among allies and partners often adrift in a sea of abstract theory towards unrealized norms – unable to recognize or articulate mistakes or different courses of action that might avoid them. It is also highly likely that the planners of an effects operation intended to generate highly visible disruption, with associated messaging for psychological impact, will have anticipated detection and disclosure of the tooling used to deliver these effects, and made operational choices accordingly that would minimize potential degradation of future options.

Addressing this present situation is in its own way potentially problematic. Real concerns exist where such conversations may lead hostile intrusion and attack campaigns to “improve” ways that advance their sophistication and capacity to inflict harm on defenders, or to defang the rare access and effects opportunities available to states acting with restraint and responsibility. There is also a high likelihood that adversaries will continue to ignore notions of responsibility grounded in the global international order to which they are inimically opposed, and that they see as offering only cost without advantage. Yet it may be argued that many emerging offensive programs might seek to behave more responsibly, either out of organizational self-interest in avoiding detection and associated blowback, or even from individual operators’ recognition that spying and fighting “in the machine” is a professional activity. Nobody wants to be an intelligence service or national cyber command’s equivalent of script kiddie.

The current case also highlights the importance of understanding incidents not only individually, but also within the wider context of ongoing operations. The campaign is the proper unit of analysis for cyber conflict.[55] Here, the identified campaign – encompassing both the actions by the Indra phase and the Predatory Sparrow phase of employment of a common malware family, must also be seen in the context of regional actions impacting transportation sector targets. The strike against the Iranian railway network comes against the backdrop of repeated incidents involving kinetic attacks on maritime shipping and regional oil and gas industry targets. In no small part, such mining incidents and missile fires must also be understood in light of recurring compromise of regional port and shipping targets.[56] Earlier unattributed exchanges have also resulted in disruption at Iranian ports, including effects that appeared to impact sanctioned Iranian state entities.[57] Yet the regime has reportedly continued to fund novel offensive cyber capabilities development intended to destroy vessels at sea and to execute further loitering munitions attacks.[58]

It is only when stepping back to view the whole of the ongoing clandestine conflict that the most significant aspects of responsibility in the present case may be understood. In comparison to other ongoing exchanges of lethal fires and destructive cyber effects within the region, the action against the Iranian rail network must be seen as exceptionally measured. It is in some ways a very real reminder of competing interests that oppose the regime, and that responses even when confined to the cyber domain do not necessarily have to conform to the precise parity of targets introduced by the adversary. Rather, here the theocracy has employed its transportation assets to further ongoing proliferation and regional terror attacks, and has directly targeted other countries’ civil transport through its own attacks. This brought the theocracy’s own transport networks to the table, as potential targets of reciprocal action.

This also brings to the forefront what may be assessed as the most likely intent of the cyber attack against the railway target. A very visible demonstrative action against a representative target, within strong restraints and executed in a deliberately responsible fashion, highlights the pervasive vulnerability of Iranian networks to potential disruption and destruction but risks little unanticipated collateral damage. The strike almost certainly involved no exquisite capabilities, and while the mechanisms of access remain unclear, these were likely commonly known exposures that the generally woeful state of Iranian cyber defenses had never appropriately remediated. The selection of this target therefore does nothing to tip the attacker’s hand as to the true extent of offensive options that might be employed in a less constrained engagement, or in a sustained campaign intending to inflict strategic costs upon the regime.

Unfortunately, however strongly intended and communicated the signal, it is constrained by the receptive capacity of the Iranian regime. There is little indication to date that the core leadership is responsive to such demonstrative actions, and it has shown continued disregard for pressure arising from a frustrated and disillusioned population. The regime’s elites continue to profit from corrupt relationships cultivated in regional adventurism, and see the near-term possibilities of further relief from crippling sanctions imposed under the prior US administration. As faltering negotiations stumble on, while clandestine acquisition activities still pursue prohibited uranium enrichment to set conditions for potential materials diversion and nuclear breakout (using expertise and technology never adequately declared, monitored, or decommissioned despite earlier agreements), the potential leverage that can be generated by restrained and responsible offensive cyber operations is rapidly declining. [59]  And in this is the real concern – that once reasonable options have been exhausted, there will remain nothing but capabilities reserved only for in extremis situations.

JD Work now serves at the Marine Corps University’s Krulak Center for Innovation and Future Warfare, and holds additional affiliations with Columbia University’s Saltzman Institute of War and Peace Studies, as well as the Atlantic Council’s Cyber Statecraft Initiative. He has over two decades experience working in cyber intelligence and operations roles for the private sector and US government.


[1] The views and opinions expressed here are those of the author and do not necessarily reflect the official policy or position of any agency of the US government or other organization.

[2] The author would like to thank Dave Aitel, Juan Andrés Guerrero-Saade, and Gary Brown for comments and critique.

[3] Winn Schwartau, Information Warfare: Chaos on the Electronic Superhighway (New York: Thunder’s Mouth Press, 1994). ; John Arquilla, David Ronfeldt, In Athena’s Camp: Preparing for Conflict in the Information Age (Santa Monica: RAND, 1997). ; Gregory J. Rattray, Strategic Warfare in Cyberspace (London: MIT Press, 2001).

[4] Reuters. “Iran transport ministry hit by second apparent cyberattack in days.” 10 July 2021.

[5] Amn Pardaz. “Trojan.Win32.BreakWin”. 13 July 2021.

[6] Islamic Republic News Agency (IRNA). ” What was the story of the cyber attacks on the Ministry of Roads and Urban Development and Railways?” 18 July 2021. (Farsi)

[7] Juan Andrés Guerrero-Saade. “MeteorExpress: Mysterious Wiper Paralyzes Iranian Trains with Epic Troll.” SentinelOne. 29 July 2021.

[8] Predatory Sparrow, social media, 9 July 2021.

[9] Flashpoint. “Inside an Iranian Hacker Collective: An Exclusive Flashpoint Interview with Parastoo”. 3 February 2016.

[10] JD Work. “Echoes of Ababil: Re-examining formative history of cyber conflict and its implications for future engagements.” Soldiers and Civilians in the Cauldron of War, 86th Annual Meeting of the Society for Military History. May 2019.

[11] Checkpoint, “Indra — Hackers Behind Recent Attacks on Iran”. 14 August 2021.

[12] Kevin Mazur, Revolution in Syria, (Cambridge : Cambridge University Press, 2021)

[13] Lucas Winter. “The Katerji Group- A New Key Player in the Syrian Loyalist Universe”. OE Watch, Foreign Military Studies Office. September 2019.

[14] Michael Georgy, Maha El Dahan. “How a businessman struck a deal with Islamic State to help Assad feed Syrians.” Reuters. 11 October 2017.

[15] Indra. Via social media. 11 February 2020.

[16] As advanced by Emily Goldman, Richard Harknett, and Michael Fischerkeller. Whilst we eagerly await their full volume forthcoming, at present one may see Michael P. Fischerkeller, Richard J. Hartnett. “Persistent Engagement and Tacit Bargaining: A Path Toward Constructing Norms in Cyberspace”. Lawfare. 9 November 2018. https://www.lawfareblog.com/persistent-engagement-and-tacit-bargaining-path-toward-constructing-norms-cyberspace ;  Michael P. Fischerkeller, Richard J. Harknett, “Persistent Engagement, Agreed Competition, Cyberspace Interaction Dynamics and Escalation.” Institute for Defense Analyses, May 2018, https:// http://www.ida.org/idamedia/Corporate/Files/Publications/IDA_Documents/ITSD/2018/ D-9076.pdf

[17] The principle is stated as Rule 93 and Rule 99 of Tallinn Manual 2.0, On the International Law Applicable to Cyber Operations (Cambridge: Cambridge University Press, 2017)

[18] International Committee of the Red Cross, Study on Customary International Humanitarian Law, Volume I, (Cambridge: Cambridge University Press, 2005), also restated in Tallinn 2.0, Rule 100

[19] Tallinn 2.0, Rule 86

[20] Tallinn 2.0, Rule 33

[21] Nils Melzer, Direct participation in hostilities under international humanitarian law (Geneva: International Committee of the Red Cross, 2009)

[22] Tallinn 2.0, Rule 87

[23] Tallinn 2.0, Rule 90

[24] Tallinn 2.0, Rule 100

[25] Wilfried Buchta, “Who Rules Iran? The Structure of Power in the Islamic Republic”, (Washington DC: Brookings Instituion Press, 2000); Frederic Wehrey, Jerrold D. Green, Brian Nichiporuk, Alireza Nader, Lydia Hansell, Rasool Nafisi and S. R. Bohandy, “The Rise of the Pasdaran:  Assessing the Domestic Roles of Iran’s Islamic Revolutionary Guards”, (Santa Monica: RAND, 2009)

[26] US Treasury Department. “Treasury Targets Vast Supreme Leader Patronage Network and Iran’s Minister of Intelligence”. 18 November 2020. https://home.treasury.gov/news/press-releases/sm1185, and network analysis of corporate relationships https://home.treasury.gov/system/files/126/most_found_11182020.pdf

[27] Tallinn 2.0, Rule 100.10

[28] Tallinn 2.0, Rule 92

[29] Michael Schmitt and Jeffrey Biller. “The NotPetya Cyber Operation as a Case Study of International Law”. EJIL Talk blog. 11 July 2017. https://www.ejiltalk.org/the-notpetya-cyber-operation-as-a-case-study-of-international-law/ ; Tarah Wheeler, John Alderdice. “The Geneva Convention and International Cyber Incidents”. Belfer Center for Science and International Affairs, Kennedy School, Harvard University. 4 February 2021. ; https://www.youtube.com/watch?v=nOOk3ltPvEw ; Monica Kaminska, Dennis Broeders, Fabio Cristiano, “Limiting Viral Spread: Automated Cyber Operations and the Principles of Distinction and Discrimination in the Grey Zone”, 13th International Conference on Cyber Conflict (CyCon): ‘Going Viral’. Tallinn, Estonia. 2021.

[30] Gary D. Brown, Andrew O. Metcalf. “Easier Said than Done: Legal Reviews of Cyber Weapons”. 7 J. Nat’l Sec. L. & Pol’y 115 (2014); David Wallace, “Cyber Weapon Reviews under International Humanitarian Law: A Critical Analysis”. NATO CCDCOE. 2018.

[31] Tallinn 2.0, Rule 100.5-7

[32] Beth D. Graboritz, James W. Morford, Kelly M. Truax, “Why the Law of Armed Conflict (LOAC) Must Be Expanded to Cover Vital Civilian Data”, Cyber Defense Review 5, No 3 (2020): 121-131.

[33] Neil C. Rowe, “War Crimes from Cyber-weapons “, Journal of Information Warfare 6, no 3 (2007): 15-25; Michael N. Schmitt, “‘Attack’ as a term of art in international law: The cyber operations context”, 4th International Conference on Cyber Conflict (CYCON). Tallinn, Estonia. 2012. ; Max Smeets, Herbert S. Lin. “Offensive cyber capabilities: To what ends?” 10th International Conference on Cyber Conflict (CyCon). Tallinn, Estonia. 2018.

[34] Remarks under Chatham House rule, GlassHouse Center. 14 September 2021.

[35] Panayotis A Yannakogeorgos, Eneken Tikk. “Stuxnet as cyber-enabled sanctions enforcement”.  International Conference on Cyber Conflict (CyCon US). Washington, DC. 21-23 October 2016.; Mark Peters, “Cyber Enhanced Sanction Strategies: Do Options Exist?” Journal of Law & Cyber Warfare 6 no 1 (2017):95-154

[36] Tallinn 2.0, Rule 98

[37] Tallinn 2.0, Rule 92.2

[38] Tallinn 2.0, Rule 100.26

[39] William Michael Reisman and James E. Baker, Regulating Covert Action: Practices, Contexts and Policies of Covert Coercion Abroad in International and American Law (New Haven, CT: Yale University Press, 1992).

[40] Alexandra H. Perina, “Black Holes and Open Secrets: The Impact of Covert Action on International Law”, 53 Colum. J. Transnat’l L. 507 (2014-2015)

[41] Lawrence Lessig, Code and Other Laws of Cyberspace (New York: Basic Books, 1999)

[42] Perri Adams, Dave Aitel, George Perkovich, JD Work. “Responsible Cyber Offense”. Lawfare. 2 August 2021. https://www.lawfareblog.com/responsible-cyber-offense

[43] Gary Brown, “Spying and Fighting in Cyberspace,” Journal of National Security Law & Policy, 2016

[44] JD Work. “Who Hath Measured the (Proving) Ground: Variation in Offensive Capabilities Test and Evaluation.” 15th International Conference on Cyber Warfare and Security. Old Dominion University, Norfolk, VA. March 2020.

[45] Dragos. “EKANS Ransomware and ICS Operations”. 3 February 2020.

[46] 冉晓径 (Ran Xiaojing), “浅谈模拟集群通信系统在伊朗铁路中应用” (“On the Application of Analog Trunk Communication System in Iranian Railways”), 铁道通信信号 (Railway Communication Signal) 46 no 6 (2010).

[47] Javad Lessan, Ahmad Mirabadi, & Yaser Gholamzadeh Jeddi, “Signaling system selection based on a full fuzzy hierarchical-TOPSIS algorithm”,  International Journal of Management Science and Engineering Management 5, No 5 (2010): 393-400. M. Tamannaei, M. Shafiepour, H. Haghshenas, B. Tahmasebi, “Two Comprehensive Strategies to Prioritize the Capacity Improvement Solutions in Railway Networks”, International Journal of Railway Research 3, No 1 (2016):9-18; Mohammad Ali Sandidzadeh, Farzaad Soleymaani, Shahrouz Shirazi, “Design and Implementation of a Control, Monitoring and Supervision System for Train Movement Based on Fixed Block Signaling System with AVR Microprocessor,” Materials Science and Engineering 671 (2020)

[48]  Christian Schlehuber, Erik Tews, Stefan Katzenbeisser, “IT-Security in Railway Signalling Systems.” In Reimer H., Pohlmann N., Schneider W. (eds) ISSE 2014 Securing Electronic Business Processes. (Wiesbaden: Springer Vieweg, 2014); Sergey Gordeychik, Aleksandr Timorin. “The Great Train Cyber Robbery”. Chaos Communications Congress, Hamburg. 27 December 2015.

[49] M. Yaghini, F. Ghofrani, S. Molla, M. Amereh, B. Javanbakht. “Data Analysis of Failures Of Signaling And Communication Equipment In Iranian Railways Using Data Mining Techniques”. Journal of Transportation Research 11 no 4 (2015): 379-389.

[50] Peter J. Denning. “Computer Viruses”. Research Institute for Advanced Computer Science, Ames Research Center, National Aeronautics and Space Administration. 1988. ; Eugene H. Spafford. “Computer Viruses: A Form of Artificial Life”. Purdue University. 1990

[51] JD Work. “Competitive Dynamics of Observation and Sensemaking Processes Impacting Cyber Policy (Mis)Perceptions”. Bridging the Gap Workshop, Cyber Conflict Studies Association. 12 November 2019.

[52] Dave Aitel. “A plausible platform for cyber norms”. CyberSecPolitics blog. 28 February 2016. https://cybersecpolitics.blogspot.com/2016/02/a-plausible-platform-for-cyber-norms.html; Dave Aitel. “A technical scheme for “watermarking” intrusions”. 8 March 2016. https://cybersecpolitics.blogspot.com/2016/03/a-technical-scheme-for-watermarking.html

[53] Remarks under Chatham House rule, GlassHouse Center, 30 July 2021

[54] Such ethical dilemmas are discussed further in Juan Andrés Guerrero-Saade. “The ethics and perils of APT research: an unexpected transition into intelligence brokerage”. Virus Bulletin Conference. Prague. 30 September – 2 October 2015.; JD Work. “Ethics considerations in victimology collection & analysis in cyber intelligence.” Legally Immoral Activity: Testing the Limits of Intelligence Collection. The Citadel, Charleston. 12 February 2020.

[55] This point has been made frequently within the community of practice, but additional by scholars including Richard J. Harknett and Max Smeets, “Cyber campaigns and strategic outcomes”, Journal of Strategic Studies (2020)

[56] JD Work. “Counter-cyber operations and escalation dynamics in recent Iranian crisis actions”, Workshop on Crisis Stability and Cyber Conflict, Columbia University. February 2020.

[57] JD Work and Richard J. Harknett. “Troubled Vision: Understanding recent Israeli-Iranian offensive cyber exchanges.” CyberStatecraft Initiative, Atlantic Council. July 2020. https://www.atlanticcouncil.org/in-depth-research-reports/issue-brief/troubled-vision-understanding-israeli-iranian-offensive-cyber-exchanges/

[58] Jeremie Binnie. “CENTCOM identifies Iranian delta-wing UAV used in tanker attack” Jane’s Intelligence. 9 August 2021. ; Deborah Haynes. “Iran’s Secret Cyber Files”. Sky News. 27 July 2021. https://news.sky.com/story/irans-secret-cyber-files-on-how-cargo-ships-and-petrol-stations-could-be-attacked-12364871

[59] International Atomic Energy Agency. “Verification and monitoring in the Islamic Republic of Iran in light of United Nations Security Council resolution 2231 (2015)”. GOV/2021/39. 7 September 2021. Derestricted.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: