Starting from the End: What to do when Restricted Data is released | Zendy

Marta Teperek | Zendy; Rhys Morgan | Zendy; Michelle R. Ellefson | Zendy; Danny Kingsley | Zendy

AI Assistant Blog Pricing

Home ZAIA Blog

Open Access

Starting from the End: What to do when Restricted Data is released

Author(s) -

Marta Teperek,

Rhys Morgan,

Michelle R. Ellefson,

Danny Kingsley

Publication year - 2017

Publication title -

data science journal

Language(s) - English

Resource type - Journals

SCImago Journal Rank - 0.358

H-Index - 21

ISSN - 1683-1470

DOI - 10.5334/dsj-2017-010

Subject(s) - computer science , workflow , subject (documents) , hacker , data science , data breach , computer security , internet privacy , data security , world wide web , database , encryption

Repository managers can never be one hundred percent sure of the security of hosted research data. Even assuming that human errors and technical faults will never happen, repositories can be subject to hacking attacks. Therefore, repositories accepting personal/sensitive data (or other forms of restricted data) should have workflows in place with defined procedures to be followed should things go wrong and restricted data is inappropriately released. In this paper we will report on our considerations and procedures when restricted data from our institution was inappropriately released

The content you want is available to Zendy users.

Already have an account? Click here to sign in.

Having issues? You can contact us here

Accelerating Research