Turing Safe Data Use Policy

[bw-faststream]

As we've now got the classification web-app and safe haven design to a stage where its mostly usable, I'm writing a Turing standards policy for safe data use on projects, based on past documents and other chats about how the process should work. Roughly, the structure should take the form of:

• When you need to classify data
• Roles and responsibilities
• How to classify data
• What the data classifications mean
• How should you work with higher classification data

[jemrobinson]

Does anyone know whether @bw-faststream finished doing this?

[jemrobinson]

@martintoreilly @kevinxufs could you confirm whether @bw-faststream ever finished this and close the issue if appropriate?

[kevinxufs]

So I've taken a look at some of Ben's work in this area @jemrobinson

These documents are largely found in the the Safe Haven one drive -> archive -> Ben Walden handover documents

• When you need to classify data

There is a classification user guide which covers this

• Roles and responsibilities

There is a classification user guide which covers this

• How to classify data

There is a classification user guide which covers this, as well as different diagrams

• What the data classifications mean

There's a rather in depth diagram with comments titled Data Classification Tiers - Comments. I'm not sure if this is complete. We have seperate documentation in what individual tiers mean. There's a best practice guide for sensitive data handling guide

• How should you work with higher classification data

There's a best practice guide for sensitive data handling guide

I think it all looks fairly comprehensive. Closing for now.

[jemrobinson]

@kevinxufs : is the user guide in Sharepoint the same as https://github.com/alan-turing-institute/data-safe-haven/blob/master/docs/safe_haven_data_classification_guide.md? Is the best practice guide anywhere in the repo? I'd prefer for these guides to be in the repo (as markdown) rather than in Sharepoint if possible.

[kevinxufs]

@jemrobinson

The user guide in the repo looks like it is the most updated version.

Adding the best practice guide to the repo, and other guides.

See PR #813