✨ Add manage data spills page #64
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
znatty22
force-pushed
the
manage-data-spill
branch
from
6fbc18b to
3319157
Compare
znatty22
commented
Feb 21, 2019
| IDs in the raw clinical data provided by Kids First researchers | ||
| (i.e. PID0001, SS-H02, etc.) | ||
|
|
||
| One caveat is that you can have sensitive data inside a **private Kids First |
znatty22
requested review from
allisonheath,
alubneuski,
baileyckelly,
dankolbman,
bdolly,
fiendish,
parimalak,
XuTheBunny and
liberaliscomputing
znatty22
force-pushed
the
manage-data-spill
branch
from
ee2c4ca to
316fa98
Compare
|
Should we include secrets in here too? Or make another document on cleaning those up? |
|
@dankolbman Yes, I think we should definitely have some guidelines on dealing w compromised secrets. We could probably have it in the larger data spills section but have a separate page for it if you think the checklist of actions to take will be a lot different |
znatty22
force-pushed
the
manage-data-spill
branch
from
316fa98 to
06157f7
Compare
znatty22
commented
Feb 22, 2019
| A data spill is the accidental or deliberate exposure of information into an | ||
| uncontrolled or unauthorised environment, or to persons without a need-to-know. | ||
|
|
||
| There are many examples of data spills, but for the purposes of this guide, |
There was a problem hiding this comment.
Per @dankolbman's comment on secrets - we could change the intro a bit:
we will focus on two kinds of sensitive data: clinical research data and secrets. This page will provide guidelines on what to do if this data is exposed in a public GitHub repository.
allisonheath
approved these changes
Apr 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.