Skip to content

first bits of security content added #8

Draft
sckott wants to merge 2 commits intomainfrom
security
Draft

first bits of security content added #8
sckott wants to merge 2 commits intomainfrom
security

Conversation

@sckott
Copy link
Copy Markdown
Member

@sckott sckott commented Nov 1, 2023

Any thoughts on the first bits of content for the security chapter?

This is a bit different from the other chapters in that i imagine we want to think harder about this chapter given where we work.

There's some half finished thoughts on purpose in here for your feedback. thanks!

We're only building the book for congtent on main, but you can pull this repo down, then run make preview

#6

@sckott
Copy link
Copy Markdown
Member Author

sckott commented Nov 3, 2023

bump @seankross 🙏🏽

Comment thread security.qmd

### Examples

We strongly encourage all exported, user-facing functions, to have examples. However, when PII/PHI data is a crucial part of an example for a function/class/etc. we need to take extra precautions.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that anything in the WILDS would have PII/PHI data. If data is de-identified, it's not considered to be PHI.

I am not sure how I am going to do data-as-a-product on the CARDS platform and if would be possible/advisable to create R packages that someone live just on there. I think that is the only time that we would have PHI in an R package though.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, thanks very much @monicagerber ! Do you think we just remove this comment about PII/PHI data in examples?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely nothing in WILDS should contain PII/PHI in the package itself, but I imagine several WILDS packages will touch/transmit PII/PHI.

Comment thread security.qmd

## Data

Software created in the WILDS may touch PII/PHI data.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that instead of writing sensitive data handling practices here we should link to the sciwiki or something.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay. Are you thinking we just remove this chapter? Or keep the chapter but simply link out to sciwiki/other resources with very little text in the chapter itself?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep it and link out. The we could have sections like "how to securely integrate [a WILDS thing] with [a service discussed on sciwiki]"

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

@sckott
Copy link
Copy Markdown
Member Author

sckott commented Mar 27, 2024

This chapter is on hold for now ...

@sckott sckott marked this pull request as draft March 29, 2024 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants