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.

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

Check for PHI/PII in AWS S3 assets #2

Open
nutjob4life opened this issue May 28, 2024 · 0 comments
Open

Check for PHI/PII in AWS S3 assets #2

nutjob4life opened this issue May 28, 2024 · 0 comments
Assignees
Labels
⬇️low Low priority

Comments

@nutjob4life
Copy link
Member

According to email from @hoodriverheather in <MW4PR09MB9122F03BDE7B64F96E8384B5C5E32@MW4PR09MB9122.namprd09.prod.outlook.com>:

Check for de-id in any image zip files in AWS. Sftp buckets, backups, etc.

Look in buckets listed here - https://docs.google.com/spreadsheets/d/18u4zNPtjN_8k-e7bgp2yrIrf-t_11phPyl0cXxBII0c/edit#gid=666247863

In the spreadsheet mentioned, the tab is "SFTP Access" and the column is F. As of this writing there are 45 unique values in column F. The general approach is probably:

  1. Create a new, "empty" instance of the LabCAS backend
  2. Sync the data from the bucket path from one row in column F
  3. Use the LabCAS publication to publish the data to the empty instance
  4. Use the Solr schema term display to manually look for anything that might be PHI or PII
  5. Repeat for the next row

N.B.: Because of the size of the data (and the manual scan) this is going to take a long time to complete.

@nutjob4life nutjob4life added the ⬇️low Low priority label May 28, 2024
@nutjob4life nutjob4life self-assigned this May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⬇️low Low priority
Projects
None yet
Development

No branches or pull requests

1 participant