Data egress process#
Data Safe Havens are used for doing secure data research on a single ‘work package’ of data. Once you have finished working with the data for your project, you’ll have to egress any outputs of your work before the environment is shutdown.
Classification#
The first stage of egressing outputs is to classify them. This follows the same workflow as for data ingress.
Hint
Get the same people who ran the ingress classification process to do this - Data Provider Representive, Investigator and Referee (optional).
Note
Each time you want to bring code or data out of the environment, you’ll have to classify this data as a new work package.
Bringing data out of the environment#
Once the classification is agreed, make sure that your Dataset Provider Representative discusses the best way to extract your outputs from the environment with your System Manager.
Note
You might want to define multiple data collections for egress, which would each have their own sensitivity classification. For example, you might separate a low-sensitivity written report from a high-sensitivity derived dataset.