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

security considerations recognizing measure definitions #82

Open
JohnMoehrke opened this issue May 15, 2020 · 1 comment
Open

security considerations recognizing measure definitions #82

JohnMoehrke opened this issue May 15, 2020 · 1 comment
Labels
Connectathon 24 Issues from Connectathon 24

Comments

@JohnMoehrke
Copy link
Collaborator

now that I understand the multi-layered approach in SANER regarding profiling vs measure definition; the security considerations section should be more clear about the security assessment of SANER, vs the security assessment of any specific measure definition, vs choices an implementation may further make.

  • SANER core would stick with public declaration needing only anonymous read as a baseline
  • SANER would recommend careful design of measure definitions to avoid sensitive data
  • might SANER have specific definitions for the CDC and FEMA measure definition?
@JohnMoehrke JohnMoehrke self-assigned this May 15, 2020
@keithboone keithboone added the Connectathon 24 Issues from Connectathon 24 label May 30, 2020
@JohnMoehrke JohnMoehrke removed their assignment Mar 30, 2022
@JohnMoehrke
Copy link
Collaborator Author

removed my assignment as I am not sure if this is still an issue or how I would determine that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connectathon 24 Issues from Connectathon 24
Projects
None yet
Development

No branches or pull requests

2 participants