Create cybersecurity-risk.md

docs/structure/cybersecurity-risk.md

@@ -0,0 +1,43 @@
+# Cybersecurity risk
+
+## Charter
+
+This is the main document to refer to,
+it should contain all of the below and further detail: [CyberSec Risks Working Group Charter](https://docs.google.com/document/d/1KLIeB4uDDxwYT7pxj5ImHa5p_3wJ2KILsVKuAl7LQlM/edit?usp=sharing)
+
+
+## Overview
+
+This working group is an opportunity for the UK TRE Community to explore issues related to the management and communication of cyber security related risks in TREs. 
+
+General guidance on cyber security management, risk identification and mitigation, and good cyber security practice for service providers and software developers is readily available. However, specific guidance in the context of TREs is not, and this group aims to provide that guidance by defining requirements such as type of tools to be used, and their purpose in a TRE. Concrete example implementations will be provided, but the principles will be more generally applicable.
+
+## Co-chairs and contact
+
+- Co-Chairs:
+ - Donald Scobbie (EPCC)
+ - Martin O’Reilly (The Alan Turing Institute)
+
+- Contact: Donald Scobbie ([email protected])
+
+The main communication channels for the WG will be:
+
+- The WG email list (tbd)
+- The WG Slack channel
+- Regular UK TRE Community webinar events and presentations
+
+
+## How to get involved
+
+(mailing list, slack channel, repositories…)
+
+[Working Group repository](https://github.com/uk-tre/cybersec-wg) will be prioritized for involvement in this working group
+
+The main communication channels for the WG will be:
+
+- The WG email list (tbd)
+- The WG Slack channel
+- Regular UK TRE Community webinar events and presentations
+
+The working group will progress as a series of ‘task and finish’ exercises to complete specific work related to tools, processes and documents. Contributors will be encouraged to participate in the working group at task level so that contributions can be short term, focussed, and benefit from specific skills.
+