Scenario 07: Leak of State-developed hacking tools
Jump to navigation
Jump to search
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
fill this in!
=== Attribution to State B === '''[L11]''' Incidents 1-2 are not attributable to State B – there is no indication of State B’s involvement in the leak of vulnerabilities. Incident 3 (the ransomware campaign) is attributable to State B, because the operation was conducted by one of its military units, which qualifies as an [[Attribution|organ of the State]].<ref>ILC [http://legal.un.org/ilc/texts/instruments/english/commentaries/9_6_2001.pdf Articles on State Responsibility], Art 4(1); [https://doi.org/10.1017/9781316822524 Tallinn Manual 2.0], commentary to rule 15, para 1; see also ICRC Customary IHL Study, vol 1, 530–531 (“The armed forces are considered to be a State organ, like any other entity of the executive, legislative or judicial branch of government.”).</ref>
Please note that all contributions to International cyber law: interactive toolkit are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) (see
International cyber law: interactive toolkit:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
(opens in new window)
Retrieved from "
Not logged in
What links here
Get shortened URL