Data egress#

Purpose#

Research outputs must be brought out of the Turing TRE. These may include data, code or other artifacts. The purpose of this document is to define the security procedures around data egress.

Scope#

This procedure covers all data and code egress for all projects running in the Turing TRE.

Responsibilities#

Role

Responsibility

🧑‍🔬 Project team

Prepare artifacts for egress

🧑‍💻 Trusted research data manager

Assessing whether requested artifacts are appropriate for egress

🧑‍🔧 Trusted research system administrator

Assisting project team in moving data out of the TRE to an appropriate location

Authorised release contact

Downloading outputs to their own system

Procedure#

  1. 🧑‍🔬 Project team: Fill out the Turing TRE Data Egress Request form and place the requested artifacts in the egress folder inside the TRE.

  2. 🧑‍💻 Trusted research data manager: Review the Turing TRE Data Egress Request form and any supporting documents. If any changes are needed, discuss these with the 🧑‍🔬 Project team and amend the form accordingly.

  3. 🧑‍💻 Trusted research data manager: Send it to be DocuSigned by each of the appropriate responsible people named on the Turing TRE Project Initialisation form

  4. 🧑‍💻 Trusted research data manager: Place the signed form in the data-egress ‣ signed folder in Sharepoint

  5. 🧑‍🔧 Trusted research system administrator: Generate a SAS token following the DSH System Manager instructions

  6. 🧑‍🔧 Trusted research system administrator: Send the SAS token to the authorised release contact via secure email.

  7. 🧑‍🔧 Trusted research system administrator: Work with the authorised release contact to help them download the data using one of the approved methods below: