Toolkit macrostructure

From International cyber law: interactive toolkit
Jump to navigation Jump to search

note from Tomáš: I edited the MediaWiki:Common.css to allow overriding the automatic numbering in our wiki according to https://www.mediawiki.org/wiki/Manual:Table_of_contents#Auto-numbering.

(note to team: think of a good acronym / codename for the toolkit)

Initial notes[edit | edit source]

I think the most important rule is to avoid ‘feature creep’. The focus of the project is on scenarios – let’s have that done by March 2019 – everything else should facilitate this goal. If the project is extended, we can keep adding features. Therefore, I would not try to include exercises at this point. We can use some of the injects for designing the scenarios instead.

We should focus on legal advisors, not decision-makers. Primarily, legal advisors from the defence community; secondarily, intelligence services, law enforcement, cyber security agencies.

We should focus on rank-and-file legal advisors; we should not presuppose a particularly detailed knowledge of international law, cyber law, or ICT on the part of the audience.

Landing page structure[edit | edit source]

Examples:

https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Arts

https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Science

https://www.law.cornell.edu/

http://eu4.paradoxwikis.com/Europa_Universalis_4_Wiki

After a careful consideration, the EU4 wiki was selected as the model landing page (nice and simple).

Types of articles[edit | edit source]

Scenarios[edit | edit source]

(according to project, at least 12 case studies falling into three main categories: (i) general international law; (ii) peacetime cyber operations; (iii) cyber law of armed conflict.)

This should be developed after we have a more comprehensive list of real-world examples (3.3.)

Here is Scenario 101.

Areas of law[edit | edit source]

(this is a representative selection from Tallinn Manual 2.0 table of contents)

General international law and peacetime cyber operations[edit | edit source]

Cyber law of armed conflict (JAB, JIB)[edit | edit source]

It is probable that we will have to cover most of these topics. However, since the project is focused on scenarios, there is no need to cover all of them by March 2019.

Real-world examples[edit | edit source]

  • (...)
  • Estonia 2007
  • Georgia 2008
  • U.S. cyber operations in Iraq since 2003
  • Heartbleed (what happens when a widespread vulnerability is disclosed)
  • Sony hack
  • OPM hack
  • DNC hack
  • Stuxnet
  • WannaCry (with the twist of possible US responsibility for hoarding and not securing the vulnerabilities)
  • NotPetya
  • Ababil (2011–13)
  • Sands Casino (2014)
  • Steel mill in Germany (2014)
  • Bundestag hack (2015)
  • Power grid in Ukraine (2015)
  • Shamoon 2.0 (2016)
  • French elections (2017)
  • (...)

This list is far from representative. I will think about it some more.

The descriptions should be really short and should focus on the legally significant aspects of the incidents. Alternatively, we could use external links to reputable news sources instead.

Keywords page(s)[edit | edit source]

  • Can be based on the list of articles (similar to Categories in Wikipedia, e.g. https://en.wikipedia.org/wiki/Category:Architecture)
  • Can also contain shorter definitions of various terms (technical / legal?)
  • Can be a single page (glossary), or multiple pages (wiktionary).
  • I think we should rely on external links for most technical definitions (to avoid feature creep).

Media (pictures, videos etc.)[edit | edit source]

Will there be any? Can it help our main goal?

Structure of articles[edit | edit source]

This is based on https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Layout. See e.g. https://en.wikipedia.org/wiki/Waterloo_Medal_(Pistrucci).

The details will vary among articles based on 3.1.-3.4.

Lead section[edit | edit source]

may not be necessary for shorter articles

Table of contents[edit | edit source]

Content[edit | edit source]

Issue-rule-analysis could be the right structure for Scenario (3.1.) articles. Let’s test it.

Appendix sections[edit | edit source]

See also[edit | edit source]

Links to within the wiki.

Notes and references[edit | edit source]

Interlinked with bibliography and external links.

Bibliography / Further reading[edit | edit source]

Mostly books and other comprehensive publications.

External links[edit | edit source]

Links to webpages outside the wiki.

Misc[edit | edit source]

Hosting[edit | edit source]

NATO CCD COE – need to check technical and design requirements.

TM-2018-06-27: After talking to Lukáš B and Raik J, it might be a good idea to use external hosting with an integrated engine.

TM-2018-06-28: I checked the following options:

Wikia (Fandom)[edit | edit source]

Pros:

  • It looks like Wikipedia.
  • Should be easy to edit.
  • Very good Alexa rank (58).

Cons:

  • It is difficult to block random users from viewing / editing the product.
  • The site’s focus is on pop culture (movies, games).
  • They do not provide SSL (HTTPS).
  • Too many random ads on the pages.
  • The wiki will stay around if we decide to migrate.

Google sites[edit | edit source]

Pros:

  • They provide SSL (HTTPS).
  • It can be linked to our google accounts and services – easy to keep private during development.
  • Stability – Google is behind it.

Cons:

  • It doesn’t look like Wikipedia.
  • There is no easy way to make it look like Wikipedia.
  • It’s not easy to migrate.

Wikiversity[edit | edit source]

Pros:

  • It looks like Wikipedia.
  • SSL is provided.
  • Stability - it is directly linked to the Wikimedia foundation and Wikipedia.
  • Its focus corresponds to the objectives of our project.
  • Good Alexa rank (10,901).

Cons:

  • It is difficult to block random users from viewing / editing the product under development.
  • Despite their links to the Wikimedia foundation, the project looks very much under construction.

Miraheze[edit | edit source]

Pros:

Cons:

  • They can delete the wiki if it is dormant for too long.
  • It can be more difficult to set up a WYSIWYG editor – I am currently checking this – but I am fine with code.

TM-2018-06-28: Today I was considering Wikiversity vs. Miraheze. Since this page is being created in Miraheze, it is clear which one I chose. See the advantages above; the most important reason was that it can be kept private during development.

Technical solution (wiki engine)[edit | edit source]

Options:

  • MediaWiki
  • MoinMoin
  • WikiCreole
  • Dokuwiki
  • Zim

Needs to be reliable when online (bugs and security) and allow for data portability and reliable backup.

TM-2018-06-27: the engine will depend on the hosting, but MediaWiki seems to be the most suitable.

Licence for the content[edit | edit source]

Options:

  • CC-BY?
  • CC-BY-NC?
  • CC-BY-SA?
  • CC-BY-SA-NC?

Need to talk to Lauri A and other stakeholders. I would prefer CC-BY, but this has to be agreed by everyone.

TM-2018-06-26: Lauri A is supportive of as open licence as possible (reasoning that the project is supported by NATO CCD COE but headed by Exeter). This means that the options are CC-BY or CC-BY-SA. It also depends on who will do the hosting and what engine will be used (see 5.2. above). For instance, wikia.com (MediaWiki) uses CC-BY-SA for most wikis.

TM-2018-06-28: Miraheze uses CC-BY-SA.

Who can edit and view the wiki?[edit | edit source]

Ideally, the wiki should be open to viewing by the general public. Editing should be restricted to a vetted group (Exeter University, CCD COE, NCISA, peer reviewers, friends).

TM-2018-06-28: Miraheze provides this option.

List of sources[edit | edit source]

Treaties[edit | edit source]

Case-law[edit | edit source]

Other sources[edit | edit source]

original content of the Main Page for reference[edit | edit source]

This Main Page was automatically created by a wiki creator (a volunteer who created this wiki per a request), and it seems it hasn't been replaced yet.

For the bureaucrat(s) of this wiki[edit | edit source]

Hello, and welcome at your new wiki! Thank you for choosing Miraheze for the hosting of your wiki, and we hope you will enjoy our hosting.

You can immediately start working on your wiki, whenever you want.

Need help? No problem! We will help you with your wiki as needed. To make a start we have added a few links about working with MediaWiki:

But Miraheze, I still don't understand X![edit | edit source]

Well, that's no problem. Even if something isn't explained in the documentation/FAQ, we still are happy to help you. You can find us here:

For a visitor of this wiki[edit | edit source]

Hello, the default Main Page of this wiki (this is the default Main Page) has not been replaced yet by the bureaucrat(s) of this wiki. The bureaucrat(s) might still be working on a Main Page, so please check this page again later!