You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why do we need a Standard Architecture for TREs has no question mark in link/anchor
suggest to add
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 frameworks or regulations that may apply to TREs such as ISO27001 or 5 Safes. However these don't provide presecriptive guidance on how TREs comply or achieve accreditation. In recognition of this, SATRE aims to find the commonalities and compile a resource for TRE Operators, Builders and Developers to refer to and benefit from. See 👀 What is SATRE? for more information.
What do TRE Builders/Developers gain by reading the SATRE specification?
Is it necessary to say what the specification is not?
The SATRE specification provides a guide for thinking about choices which need to be made and what capabilities the TRE should possess. By reading through the SATRE specification, developers tasked with designing and/or building a TRE for sensitive data projects can avoid re-inventing the wheel.
Who can help
No response
The text was updated successfully, but these errors were encountered:
Summary
Suggestions on FAQs
Source
Personal contribution
Detail
Specific suggestions below also comments on
My TRE is designed for data that doesn’t require this level of protection. Should I still follow SATRE?
Is there value in referencing tiering per the Turing paper in this FAQ?
Does SATRE describe approaches to TRE federation or interoperability of TREs?
Is it worth referencing the DARE UK blueprint and links between this and other Driver projects?
Where
https://satre-specification.readthedocs.io/en/latest/faqs.html
Proposal
Why do we need a Standard Architecture for TREs has no question mark in link/anchor
suggest to add
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 frameworks or regulations that may apply to TREs such as ISO27001 or 5 Safes. However these don't provide presecriptive guidance on how TREs comply or achieve accreditation. In recognition of this, SATRE aims to find the commonalities and compile a resource for TRE Operators, Builders and Developers to refer to and benefit from. See 👀 What is SATRE? for more information.
What do TRE Builders/Developers gain by reading the SATRE specification?
Is it necessary to say what the specification is not?
The SATRE specification provides a guide for thinking about choices which need to be made and what capabilities the TRE should possess. By reading through the SATRE specification, developers tasked with designing and/or building a TRE for sensitive data projects can avoid re-inventing the wheel.
Who can help
No response
The text was updated successfully, but these errors were encountered: