Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates faqs.md based on #282 proposal #302

Merged
merged 3 commits into from
Oct 11, 2023
Merged

Updates faqs.md based on #282 proposal #302

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d4f9d06
Updates faqs.md based on #282 proposal
Oct 11, 2023
4ab6040
Update docs/source/faqs.md
manics Oct 11, 2023
c395b16
pre-commit run -a
manics Oct 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/source/faqs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,11 @@ For more information about TREs, visit the [UK TRE Community website](https://ww

(why_satre)=

## Why do we need a Standard Architecture for TREs
## Why do we need a Standard Architecture for TREs?

A variety of approaches have been taken to building computing infrastructure and designing processes and policies for research with sensitive data.
There are also a range of standards or frameworks that may apply to TREs such as [ISO27001](https://www.iso.org/standard/27001) or [5 Safes](https://blog.ons.gov.uk/2017/01/27/the-five-safes-data-privacy-at-ons/).
However, they don't provide prescriptive guidance on how TREs comply or achieve accreditation.
In recognition of this, SATRE aims to find the commonalities and compile a resource for TRE {ref}`Operators, Builders and Developers <infrastructure_roles>` to refer to and benefit from.
See {ref}`what_is_satre` for more information.

Expand Down
Loading