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

Access control #197

Open
AnnaFeiler opened this issue Jul 24, 2023 · 1 comment
Open

Access control #197

AnnaFeiler opened this issue Jul 24, 2023 · 1 comment
Assignees
Labels
SES Safety, Effectiveness, Security related issue

Comments

@AnnaFeiler
Copy link
Collaborator

AnnaFeiler commented Jul 24, 2023

Since most hospitals currently don't support access control, we need to provide allowlists for our devices.

  • Define a common format for allowlists
  • Specify the allowlist format in SDPi - use of allowlists is not mandatory, if hospitals can do access control in a different way. If they are used, they need to follow the defined format.
  • If needed, specify how to improve access control in the future without using allowlists
@AnnaFeiler AnnaFeiler added the Comment NEW A submitted comment waiting to be reviewed and dispositioned label Jul 24, 2023
@AnnaFeiler AnnaFeiler added this to the SDPi 1.3 Review milestone Jul 24, 2023
@AnnaFeiler AnnaFeiler added the SES Safety, Effectiveness, Security related issue label Jul 24, 2023
@ToddCooper ToddCooper removed the Comment NEW A submitted comment waiting to be reviewed and dispositioned label Jul 28, 2023
@ToddCooper
Copy link
Collaborator

@MartinKasp - this is a simple list of endpoint references
Question also about similar approaches in common use in hospitals (e.g., OAuth) (note: gRPC & FHIR use).
Do not want to "reinvent the wheel" ... especially in the area of cybersecure devices
NOTE: TF-2 Appendix C Security will be the place to collect this information.

@AnnaFeiler AnnaFeiler changed the title Define the format of the allowlist Access control Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SES Safety, Effectiveness, Security related issue
Projects
Status: New issues
Development

No branches or pull requests

5 participants