Good morning,
lets see of i can help with this ...
A metadata-bound Library is a physical library that is tied to a corresponding metadata object.
So when you create a metadata-bound library, SAS generates a new metadata object and binds
the physical library to that object.
A user must have permissions for whatever action is requested, and at the same time, the corresponding
OS id has to have the necessary permissions on the physical table.
If you'd copy data from a metadata-bound lib to another location on the OS, the security information on
that tables is still "active", meaning, the information is being copied with it. See
http://support.sas.com/documentation/cdl/en/seclibag/66930/HTML/default/viewer.htm#n14a0xp98mxlrgn1goddjmjr3ahf.htm
As for encryption:
SAS encryption works for data in transit and data at rest. Data at rest means encryption for passwords of
configuration files, metadata repositories, SAS code, SAS data sets, SAS HDAT in Hadoop and SAS
Performance Data Engine & Server (SPDE & SPDS) data.
Data in transit includes connections between SAS clients and SAS servers as well as browsers and SAS servers.
It further includes encryption of data betweeen server to server, including SAS servers or SAS servers and
Third Party servers.
The data sets in a metadata-bound libs are autmatically encrypted with the SAS proprietary encryption.
This encryption happens automatically with all data sets, whether bound to a lib or not. If AES is added as
stronger encryption key, it has to be added to the data in the metadata-bound lib.
I am not quite clear whether your mentioning of encryption is a question ?
Does that help?
Please let me know in case of any further questions.
Best
Anja
... View more