October 27, 2021 at 12:00 am
Comments posted to this topic are about the item Security Bug or Handy Feature
October 27, 2021 at 1:03 pm
Maybe what I'm describing already exists - but one method of securing shared documents or datasets would be where the data is encrypted at rest, and then when you share the data, the recipient receives a unique decryption key that works only when combined with the recipient's AD, Apple, Google, etc. login account. So, when you share a document with Tom, that data is only usable on one of Tom's devices and can't be shared with a 3rd party. There would still be nothing to prevent Tom from exporting or screen capturing the data and sending it elsewhere, but it would at least prevent the scenario where Tom accidentally publishes a mess of shared data unintentionally.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
October 27, 2021 at 10:04 pm
A lot of what you describe is handled already with things like o365 and Sharepoint. Keys and access are shared. There is some facility for non-org users, though it's not always ubiquitous.
The downsides is the publish/share is a problem, especially across time. We need a facility built into the OS and apps to limit sharing.
October 27, 2021 at 10:04 pm
A lot of what you describe is handled already with things like o365 and Sharepoint. Keys and access are shared. There is some facility for non-org users, though it's not always ubiquitous.
The downsides is the publish/share is a problem, especially across time. We need a facility built into the OS and apps to limit sharing.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply