Skip to content

Upload cache session based isolation #1829

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

Open
dean-taylor opened this issue Apr 14, 2025 · 0 comments
Open

Upload cache session based isolation #1829

dean-taylor opened this issue Apr 14, 2025 · 0 comments

Comments

@dean-taylor
Copy link

My understanding is that the MONAILabel upload cache location is a single allocation that is shared among potentially multiple api clients. The file names within the cache are as per the original uploaded image without any obfuscation or any assurance of uniqueness.

IMO this has a number of drawbacks in utilising MONAILabel as an API presented service.

  1. There is the possibility of users uploading images with the same name and casing a conflict.
  2. There is the possibility of potentially sensitive images to be accessed via unauthorised users.

This could greatly reduce the potential use cases and operational workflows of MONAILabel.

I would like MONAILabel to implement a level of isolation and/or obvuscation within the cache to ensure access of images is a 1:1 with user access. This could be linked to a specific user session.

ATM we are ensuring that MONAILabel implementations are dedicated to a single individual or group via infrastructure segregation. Either by running the API on a specific host or measures of network microsegmentation and that the implementation is ephemeral in nature.

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

No branches or pull requests

1 participant