On Fri, Jun 28, 2019 at 6:39 AM Mark Jacobs < [email protected]> wrote:
> Outside of using dataset conditional access rules is there anyway to > prevent someone from copying encrypted dataset HLQ1.data to HLQ2.data? They > have access rights to both HLQ's and the encryption key. > Multi Level Security? Or maybe Security Labels? I don't really know anything except that these things exist. And that, at least with MLS, you cannot "write down", but you can "write up". I.e. you cannot copy from high security to low, but under the proper conditions you can copy from low to high./ > > Mark Jacobs > > Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted > email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get&[email protected] > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Money is the root of all evil. Evil is the root of all money. With that in mind, money is made by the government ... Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
