Editing Scenario 05: State investigates and responds to cyber operations against private actors in its territory

[[File:The Bronze Soldier - panoramio.jpg|thumb|The Bronze Soldier statue in Tallinn, Estonia. Photo by Keith Ruffles (CC-BY 3.0 Unported).]]
This scenario considers a series of malicious cyber operations originating from one State’s territory and targeting private entities on the territory of another. In the course of investigation, and after failing to receive cooperation from the suspected offending State, the victim State opts to penetrate the networks of the suspected offending State without consent. The victim State thereafter discovers that the suspected offending State’s military personnel was involved in some of the malicious cyber operations. This scenario analyses the rules of State responsibility, including attribution and the degrees of responsibility of the State of origin, the international obligations that may have been breached, and the ability of the victim State to justify its response under the law of countermeasures.

== Scenario ==

=== Keywords ===
DDoS, computer data, attribution, State organs, non-State actors, evidence, sovereignty, prohibition of intervention, due diligence, countermeasures

=== Facts ===
'''[F1]''' Important commercial entities and financial institutions in State A fall victim to a massive distributed denial of service (DDoS) type of campaign for several days, resulting in down-time costs that amount to millions of EUR (<b>incident 1</b>).

'''[F2]''' Later, it is found that some of the computers were infected by malware and that the data, including operating system data, had been damaged or deleted, rendering the computers inoperative (<b>incident 2</b>). Most of the targeted entities have been able to recover the data from back-ups and restore the functionality of the computers, albeit at a substantial cost. No physical damage was caused in the incidents.

'''[F3]''' The incidents have been claimed by a group called “State B Digital Army” that has been active on the Internet for some time and is openly critical of foreign policy of State A. The group bears a name clearly referring to State B, which has in the past been allegedly involved in State-run cyber espionage operations against State A. State B has never admitted any relation to the group.

'''[F4]''' The technical aspects of the first incident, or rather its lack of sophistication, seem to suggest that the attackers were just an amateur group. By contrast, the scale of the second incident indicates that a State actor could have been involved in some capacity. Also, most of the group’s activities seem to originate from the territory of State B, although the persons involved and their exact location are unknown to State A.

'''[F5]''' Considering that States A and B have not had mutual diplomatic relations for many years, that State B is uncooperative in mutual legal assistance requests, and that there is a risk of destruction of evidence by State B, State A decides to remotely access several computers in the territory of State B without State B’s consent, in the course of a criminal investigation by State A’s cyber police unit in coordination with its intelligence service (<b>incident 3</b>).

'''[F6]''' During the cyber operation against State B, State A discovers that a minority of the malicious activities indeed originated from the network of the General Staff of the Armed Forces of State B (<b>incident 4</b>). State A is also able to identify some of the individuals responsible for the attacks and consequently issues public arrest warrants for these individuals, two of whom happen to be military personnel of State B serving in cyber intelligence (<b>incident 5</b>).

'''[F7]''' State B denies all allegations, stating that the military personnel were acting on their own, outside their working hours, and it decries the “violation of its sovereignty” by State A.

=== Examples ===
* [[Cyber attacks against Estonia (2007)]]
* [[Shamoon (2012)]]
* [[Sony Pictures Entertainment attack (2014)]]
* [[Springhill Medical Center ransomware attack (2019)]]
<!--
* [[Operation Ababil (2012-2013)]]
* [[Sands Casino (2014)]]
* [[SamSam ransomware attack (2018)]]
-->

== Legal analysis ==
''For a general overview of the structure of analysis in this section, see [[Note on the structure of articles]].''

'''[L1]''' The legal analysis begins with the attribution of the incidents to States A and B, continues with possible breaches of international obligations by State B (sovereignty, prohibition of intervention, due diligence obligation) and State A (sovereignty), and ends with a possible justification for State A's response (countermeasures).

=== Attribution ===

==== State organs and exercise of governmental authority ====
{{#lst:Attribution|State organs}}
'''[L2]''' The fact that the operation against State A was partly launched from the governmental cyber infrastructure of State B, as found out in incident 4, is alone insufficient to attribute the operation to State B.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 15, para 13.</ref> However, it indicates that State B may have been associated with the operation in question.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 15, para 13.</ref> An argument for State B's involvement could be made if the network of its General Staff (as opposed to civilian governmental networks) is especially secure and unlikely to be controlled by a third Party and if the malicious activities were substantial and systematic.<ref>Compare P Margulies, '[https://law.unimelb.edu.au/__data/assets/pdf_file/0006/1687488/05Margulies-Depaginated.pdf Sovereignty and Cyber Attacks: Technology's Challenge to the Law of State Responsibility]' (2013) 14 MJIL, 16-17.</ref> Even so, there is insufficient information about a substantial or long-term involvement of State B in the activities.

'''[L3]''' Nevertheless, as soon as the two officers are identified in incident 5, the situation clearly changes: even though they might have been acting on their own (as State B claimed in the aftermath of the incidents), their conduct would still be attributable to State B. This is because the mere fact that a State organ was acting <i>ultra vires</i>, i.e., in excess of authority or in contravention of instructions, does not remove attribution from the relevant State.<ref>ILC [http://legal.un.org/ilc/texts/instruments/english/commentaries/9_6_2001.pdf Articles on State Responsibility], Art 7. </ref> It is not necessary to prove that they were getting orders from their superiors, even though such information might be helpful for the purposes of criminal investigation conducted by State A authorities.

'''[L4]''' The information available to State A after incident 5 supports only an attribution of the conduct of the military personnel of State B to that State. By contrast, there does not seem to be sufficient evidence to link State B to any of the activities of the so-called “State B Digital Army” and its supporters. That being said, there are several options under the law of State responsibility on the basis of which such conduct might in fact be attributable to State B:

==== Non-State actors ====
{{#lst:Attribution|Non-State actors}}
'''[L5]''' Options 2–4 are manifestly inapplicable to the facts of the scenario given that there is no indication that the so-called State B Digital Army was exercising any form of governmental authority or attempting to form a State of its own. Option 5 (acknowledgment and adoption) also does not apply to the present facts because State B vehemently <i>denied</i> any association with the cyber operations against State A.

'''[L6]''' The only remaining mode of attribution is that under option 1, which reflects Article 8 of the ILC’s Draft Articles on State Responsibility (i.e., the existence of instructions, direction, or control). The three standards of "instructions", "direction", or "control" can be satisfied by different conduct, but their common feature is the need to establish a form of subordination between the non-State actor and the potentially responsible State.<ref>Kubo Mačák, ‘Decoding Article 8 of the International Law Commission’s Articles on State Responsibility: Attribution of Cyber Operations by Non-State Actors’ (2016) 21 JCSL 405, 426–27 (noting that all three standards under Article 8 share the need for “a subordinate relationship between the State and the private actor”) (emphasis removed).</ref>

*The arguably most stringent factor of "instructions" would require "State B Digital Army" to be factually subordinate to State B, most commonly as an auxiliary, at the specific moment when the State decides to commit the acts in question. In this regard, the mere fact that State B and the "State B Digital Army" may have shared political goals and aims does not suffice for the purposes of attribution of the latter’s conduct to the former.<ref>Kubo Mačák, ‘Decoding Article 8 of the International Law Commission’s Articles on State Responsibility: Attribution of Cyber Operations by Non-State Actors’ (2016) 21 JCSL 405, 415 (“the fact of a goal shared by the State and the private actor is insufficient without further evidence establishing the subordination between the two”).</ref>
*The second standard would be met if an organ of State B "provided the direction pursuant to which the perpetrators of the wrongful act acted".<ref>''[https://www.icj-cij.org/files/case-related/91/091-20070226-JUD-01-00-EN.pdf Case Concerning Application of the Convention on the Prevention and Punishment of the Crime of Genocide (Bosnia and Herzegovina v Serbia and Montenegro)]'' (Judgement) [2007] ICJ Rep 43, para 406.</ref> This would imply a continuing relationship of subordination between State B and "State B Digital Army", going the beyond the mere issuance of instructions without follow-up.
*Finally, the standard of "control" similarly refers to a continuing process of exercising authority by State B over an activity such as a cyber operation – to meet this standard, State B would have to go beyond merely supporting "State B Digital Army" and would have to go on to determine the execution and course of the specific cyber operation in question.

'''[L7]''' The mere fact that some of the activities were conducted from both government and private cyber infrastructure in State B is not sufficient.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 15, para 13-14.</ref> What would need to be established is some form of subordination between the non-State actor and the potentially responsible State. As the scenario does not offer any indication of such subordination, it can be concluded that the available facts do not support the attributability of the conduct of "State B Digital Army" to State B.

==== Evidence ====
{{#lst:Attribution|Evidentiary standards}}
'''[L8]''' In incidents 1 and 2, State A does not have much information to ascertain who was responsible for the cyberattacks. Its decision to gather more evidence by launching a criminal investigation and accessing State B’s networks without asking for permission (incident 3) might be viewed as reasonable with regard to the circumstances (suspected involvement of State B), if there is no better way to obtain more evidence. This can qualify as a countermeasure of State A against State B (see the sections on extraterritorial jurisdiction and on countermeasures below). However, State A must be aware that it might be committing an internationally wrongful act if State B is not responsible for incidents 1-2, even if the hack-back seemed reasonable in the circumstances.

'''[L9]''' There is no legal obligation to publicly provide evidence upon which State A attributes the cyber operation to State B, even though States sometimes do this as a matter of good policy.<ref>According to the UK Attorney General, "the UK can and does attribute malicious cyber activity where we believe it is in our best interests to do so, and in furtherance of our commitment to clarity and stability in cyberspace. Sometimes we do this publicly, and sometimes we do so only to the country concerned. We consider each case on its merits." (UK Attorney General, Jeremy Wright QC MP, '[https://www.gov.uk/government/speeches/cyber-and-international-law-in-the-21st-century Cyber and International Law in the 21st Century]'.</ref>

=== Breach of an international obligation ===

==== Sovereignty of State A ====
{{#lst:Sovereignty|Definition}}
'''[L10]''' A violation of sovereignty on the basis of option 1 highlighted above is manifestly inapplicable as there is no indication that either incident 1 or 2 were perpetrated by entities physically present within the territory of State A.

'''[L11]''' Inherently governmental functions (options 4 and 5) were probably not affected by either incident 1 or 2 – the inability to pay invoices might have some effect on the functioning of some government organizations in State A, but the causation is probably not proximate enough given the short timeframe of the incident (several days). The organizations can postpone the payments due to unforeseeable and irresistible circumstances, which likely mitigates any adverse effects on their functions.

'''[L12]''' As for the remaining options 2 and 3, the DDoS attacks (incident 1) probably did not amount to a violation of State A’s sovereignty. There was no physical damage or injury, even though some individuals and entities in State A could be ‘physically’ affected by being unable to pay for goods and services, and there were significant economic losses as a result of the attacks. The loss of functionality was only temporary<ref>But see [https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 4, para. 14 (noting that some of the experts considered that “a temporary, but significant, loss of functionality, as in the case of a major DDoS operation” would qualify as a violation of the victim State’s sovereignty).</ref> and did not require either the replacement of physical components or the reinstallation of the operating system.

'''[L13]''' However, the deletion of data (incident 2), leading to a loss of functionality requiring the reinstallation of operating systems, could qualify as a violation of State A’s sovereignty under option 3 above.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 4, para 13.</ref> This is regardless of the fact that the affected infrastructure was non-governmental.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 2, para 3. </ref>

==== Prohibited intervention by State B ====
{{#lst:Prohibition of intervention|Definition}}
'''[L14]''' It would be difficult to argue that State B was involved in a prohibited intervention in State A’s internal affairs. To begin with, it is uncertain whether State A’s <i>domaine réservé </i>— in itself a category of relative scope under international law — was affected by incidents 1-2. The cyber activities were targeting State A’s financial sector, which is traditionally perceived as private, even if State A had a share in its ownership. Perhaps if the operations had been directed at State A’s central bank or at the integrity of financial data upon which State A’s pension or welfare system relied, this would support the qualification of the operation as an intrusion into the <i>domaine réservé</i>.<ref>Cf. Tim Maurer and Michael Schmitt, ‘[https://www.justsecurity.org/44411/protecting-financial-data-cyberspace-precedent-progress-cyber-norms/ Protecting Financial Data in Cyberspace: Precedent for Further Progress on Cyber Norms?]’ ''Just Security,'' 14th August 2017 (“In the context of financial data, an operation targeting the integrity of financial data upon which the State pension or welfare system relied in order to compel the target State to adopt a particular domestic policy would exemplify prohibited cyber intervention.”).</ref>

'''[L15]''' Even assuming that the first prong of the test was met by the cyber operations in question, there is no evidence that any of the incidents were coercive in nature as against State A. In other words, the available facts do not support any attempt to compel State A to take any action it would otherwise not take.<ref>Cf. [https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 66, para. 21 (“The key is that the coercive act must have the potential for compelling the target State to engage in an action that it would otherwise not take (or refrain from taking an action it would otherwise take).”).</ref> As such, the cyber operations in the scenario do not seem to qualify as a prohibited intervention under international law.

==== Due diligence obligation of State B ====
{{#lst:Due diligence|Definition}}
'''[L16]''' The due diligence analysis is important in the situation when State A does not have enough evidence to attribute incidents 1-2 to State B directly. If State B is in breach of its obligation of due diligence, State A might still have the option of justifying its responsive operation (incident 3) as a countermeasure.

'''[L17]''' Following from the above analysis of sovereignty, incident 2 (the deletion of data leading to a loss of functionality) is contrary to the rights of State A, and would have been unlawful if conducted by State B. It would be more difficult to similarly qualify incident 1 (the DDoS attack).

'''[L18]''' The cyber activities leading to incident 2 were conducted from the cyber infrastructure in the territory of State B; however, State B’s due diligence obligation is not breached solely by the fact that these incidents happened, even though they may have resulted in serious adverse consequences and were contrary to the rights of State A. State A would have to prove that State B had an actual or constructive knowledge of the harmful cyber activities at the time they were launched, and that it neglected its duty to terminate them.

'''[L19]''' The information that some of the harmful cyber activities were launched from State B’s government infrastructure is available to State A from incident 4 onwards. Even if it cannot be proved that State B actually gave orders to its organs, or instructed or directed the non-State actors (“State B Digital Army”) to conduct the DDoS attacks and data deletion (see the section on attribution above), the constructive knowledge requirement (“should have known”) likely triggers the breach of its due diligence obligation for the activities originating from its government cyber infrastructure.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 6, para 40.</ref> State B could argue that its government infrastructure was taken over by non-State actors or a third State, or that it did what was to be expected from a reasonable State to terminate the activities, but the burden of proof would then shift to its side.<ref>Cf. Joanna Kulesza, <i>Due Diligence in International Law</i> (Brill Nijhoff 2016) 53.</ref>

'''[L20]''' State B therefore violated its obligation of due diligence with respect to those harmful cyber activities in the scenario which made use of its governmental cyber infrastructure but could not be directly attributed to it. With respect to the conduct that is attributable to State B, that State bears direct responsibility, which supersedes any violation of due diligence.

==== Sovereignty of State B: extraterritorial jurisdiction by State A in State B ====
{{#lst:Sovereignty|Definition}}

'''[L21]''' There are two possible views as regards State A’s decision to remotely access several computers in State B’s territory in search of evidence (incident 3). On the first view, given that the resulting operation consisted merely of non-invasive collection of information, it did not as such interfere with State B’s governmental functions. By contrast, the competing view is that because the operation was mounted in order to collect evidence for criminal proceedings without the consent of the territorial State, it therefore qualified as a non-consensual exercise of law enforcement functions in State A’s territory. As law enforcement is exclusively reserved to the territorial State under international law, on this view State B’s conduct would have violated State A’s sovereignty.<ref>Compare [https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 4, para 18: “if one State conducts a law enforcement operation against a botnet in order to obtain evidence for criminal prosecution by taking over its command and control servers located in another State without that State’s consent, the former has violated the latter’s sovereignty because the operation usurps an inherently governmental function exclusively reserved to the territorial State under international law.”</ref>

'''[L22]''' State A might be able to justify its actions by invoking countermeasures, as detailed below.

=== Countermeasures by State A ===
{{#lst:Countermeasures|Definition}}
'''[L23]''' An interesting question arises at this point: is State A engaging in countermeasures against State B by exercising its enforcement jurisdiction in State B’s territory? (Let us suppose that it would be a violation of State A’s obligation to respect State B’s sovereignty, unless it is State A’s lawful countermeasure.<ref>[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 4, para 18, and to rule 11, para 7.</ref>)

'''[L24]''' We know that State B’s activities in incident 2 which can be attributed to it based on the information obtained in incidents 4-5 may amount to a violation of State A’s sovereignty, and hence an internationally wrongful act by State B; accordingly, State A would be entitled to respond with countermeasures (supposing that the effects of State B’s activities were still ongoing – for instance, if some of the deleted data could not be restored). Also, let us suppose that State A did not have the obligation to call upon State B for cessation, non-repetition, and reparation, and that it did not have the obligation to notify State B of the impending countermeasure, because that would likely defeat its purpose.

'''[L25]''' The countermeasures are not engaging a peremptory norm, nor are they affecting an obligation which would be subject to a dispute settlement procedure. The envisaged countermeasure is likely commensurate with the injury suffered. As for the purpose of the countermeasure, it serves to induce State B to comply with its obligations, because it aims to establish a firm attribution of its internationally wrongful act.

'''[L26]''' However, State A does not have the information necessary for the attribution right after incidents 1 and 2. Is State A engaging in countermeasures, if State B’s internationally wrongful act has not been established?

'''[L27]''' <i>Ex post facto</i>, it seems that the countermeasures were lawful, because State B had committed an internationally wrongful act; <i>ex ante</i>, however, State A could not have known that. Intuitively, it may seem that State A paradoxically committed an internationally wrongful act in response to an internationally wrongful act of State B.

'''[L28]''' However, the standard for the taking of countermeasures is an objective one.<ref name="ASR49">ILC [http://legal.un.org/ilc/texts/instruments/english/commentaries/9_6_2001.pdf Articles on State Responsibility], Commentary in Part 3 Chapter 2 on Art 49, para 3.</ref> The law of State responsibility does not require a subjective element to establish the wrongfulness of an act, nor does it deal with factually impossible attempts of internationally wrongful acts.

'''[L29]''' According to the commentary to the Articles on State Responsibility, “[a] State which resorts to countermeasures based on its unilateral assessment of the situation does so at its own risk and may incur responsibility for its own wrongful conduct in the event of an incorrect assessment.”<ref name="ASR49" /> Therefore, State A’s countermeasures were lawful: they were done in reaction to an objectively internationally wrongful act of State B.

== Checklist ==
* [[Attribution]]:
** How much evidence exists tying the purported perpetrators of the incidents to State B?
** What should be the evidentiary standard for making the attribution?
** Does it matter that the operation against State A was partly launched from State B's governmental cyber infrastructure?
** Does it matter that the operation against State A was partly conducted by public officials of State A?
** Can the conduct of "State B Digital Army" be attributed to State B?
* [[Sovereignty]] of State A:
** When does a cyber operation against non-State actors violate the sovereignty of a State?
* [[Prohibition of intervention]]:
** Did State B's operation intrude into State A's domaine réservé?
** Was State B's operation coercive?
* [[Due diligence]]:
** Did the relevant cyber operation adversely affect the rights of State A?
** Was the cyber operation conducted from or through the territory of State B?
** Would the cyber operation have been unlawful if conducted by State B?
** Did the incident result in serious adverse consequences for State A?
** Did State B know or should it have known of the incident in question?
** Did State B take all feasible measures to put an end to the malicious cyber activities?
* [[Sovereignty]] of State B:
** Can State A exercise its jurisdiction in State B's cyber infrastructure when trying to ascertain the attribution to State B?
* [[Countermeasures]] by State A:
** Does State A commit an internationally wrongful act by responding to an act whose wrongfulness has not been ascertained?

== Appendixes ==

=== See also ===

* [[Attribution]]
* [[Sovereignty]]
* [[Prohibition of intervention]]
* [[Due diligence]]
* [[Countermeasures]]
* [[Scenario 14: Ransomware campaign]]

=== Notes and references ===
<references />

=== Bibliography and further reading ===
* Luke Chircop, ‘[https://doi.org/10.1017/S0020589318000015 A Due Diligence Standard of Attribution in Cyberspace]’ (2018) 67 ICLQ 643.
*Gary P. Corn and Robert Taylor, ‘[https://doi.org/10.1017/aju.2017.57 Sovereignty in the Age of Cyber]’ (2017) 111 AJIL Unbound 207.
*James Crawford, ''Brownlie's Principles of Public International Law'' (OUP 2012).
*James Crawford, ''State Responsibility: The General Part'' (CUP 2013).
*Robin Geiss and Henning Lahmann, ‘Freedom and Security in Cyberspace: Shifting the Focus Away from Military Responses Towards Non-Forcible Countermeasures and Collective Threat-Prevention’ in Katharina Ziolkowski (ed), ''Peacetime Regime for State Activities in Cyberspace'' (NATO CCD COE 2013).
*James Green, ‘[https://doi.org/10.1017/S0020589308000833 Fluctuating Evidentiary Standards for Self-Defence in the International Court of Justice]’ (2009) 58 ICLQ 163.
*Wolff Heintschel von Heinegg, '[https://digital-commons.usnwc.edu/cgi/viewcontent.cgi?referer=https://www.google.ee/&httpsredir=1&article=1027&context=ils Territorial Sovereignty and Neutrality in Cyberspace]' (2013) 89 Int’l L. Stud. 123.
*Joanna Kulesza, ''Due Diligence in International Law'' (Brill Nijhoff 2016).
*Kubo Mačák, ‘[https://doi.org/10.1093/jcsl/krw014 Decoding Article 8 of the International Law Commission’s Articles on State Responsibility: Attribution of Cyber Operations by Non-State Actors]’ (2016) 21 JCSL.
*Peter Margulies, '[https://law.unimelb.edu.au/__data/assets/pdf_file/0006/1687488/05Margulies-Depaginated.pdf Sovereignty and Cyber Attacks: Technology's Challenge to the Law of State Responsibility]' (2013) 14 MJIL.
*Tim Maurer and Michael Schmitt, ‘[https://www.justsecurity.org/44411/protecting-financial-data-cyberspace-precedent-progress-cyber-norms/ Protecting Financial Data in Cyberspace: Precedent for Further Progress on Cyber Norms?]’ ''Just Security,'' 14th August 2017.
* Tomohiro Mikanagi and Kubo Mačák, ‘Attribution of Cyber Operations: An International Law Perspective on the Park Jin Hyok case’ (2020) 9 Cambridge International Law Journal 51.
*Michael N Schmitt (ed), ''[https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0 on the International Law Applicable to Cyber Operations]'' (CUP 2017).
*Michael N Schmitt, '[https://heinonline.org/HOL/P?h=hein.journals/cjil19&i=36 Virtual Disenfranchisement: Cyber Election Meddling in the Grey Zones of International Law]' (2018) 19 ChiJIntlL 30.
*Michael N Schmitt and Liis Vihul, ‘[https://texaslawreview.org/respect-sovereignty-cyberspace/ Respect for Sovereignty in Cyberspace]’ (2017) 95 Tex L Rev. 163.
*Sean Watts & Theodore Richard, '[https://law.lclark.edu/live/files/26902-lcb223article3wattspdf Baseline Territorial Sovereignty and Cyberspace]' (2018) 22 Lewis & Clark L. Rev. 771.
*Rüdiger Wolfrum, ‘Obligation of Result Versus Obligation of Conduct: Some Thoughts About the Implementation of International Obligations’ in Mahnoush H Arsanjani and others, ''Looking to the Future: Essays on International Law in Honor of Michael Reisman'' (Brill 2010).
*Katja Ziegler, “[http://opil.ouplaw.com/view/10.1093/law:epil/9780199231690/law-9780199231690-e1398 Domaine Réservé]”, in Rudiger Wolfrum (ed), ''Max Planck Encyclopedia of Public International Law'' (OUP 2008).<br />
<!--
* MN Schmitt (ed), ''Tallinn Manual 2.0 on the International Law Applicable to Cyber Operations'' (CUP 2017)
* Etc.
-->

=== Contributions ===
* Scenario by: [[People#Editorial_board|Taťána Jančárková]] & [[People#Editorial_board|Tomáš Minárik]]
* Analysis by: [[People#Editorial_board|Tomáš Minárik]]
* Reviewed by: [[People#Peer_reviewers|Russell Buchan]]; [[People#Peer_reviewers|Dan Efrony]]; [[People#Peer_reviewers|Tomáš Morochovič]]; [[People#Peer_reviewers|Peter Stockburger]]

{| class="wikitable"
|+
|Previous: [[Scenario 04: A State’s failure to assist an international organization|Scenario 04: International organizations]]
|Next: [[Scenario 06: Cyber countermeasures against an enabling State|Scenario 06: Enabling State]]
|}
[[Category:DDoS]]
[[Category:Computer data]]
[[Category:Attribution]]
[[Category:State organs]]
[[Category:Non-State actors]]
[[Category:Evidence]]
[[Category:Sovereignty]]
[[Category:Prohibition of intervention]]
[[Category:Due diligence]]
[[Category:Countermeasures]]
[[Category:Scenario]]