Perfectly said! I thank you very much! Basically what has been brought to us is to implement a way to have more security of sensitive data and strategic data. Preventing the export of raw data by unauthorized users or those who have no explicit need to do so. Avoiding actions like exporting all customer data to sell it. The important thing would be: 1. Marcello can read the data, so read permission, 2. Marcello can export the data to a spreadsheet to work on that data, so export permission. This is according to the user's level of responsibility, compliance, GDPR, or other law/regulation ... View more

So does this mean that data security depends exclusively on the user?   Can the by pass in the Metadata manager be prevented by folder permissions in the OS? ... View more

Whereas there are many ways to extract data from SAS, for example:   SAS/ACCESS to PC Files LIBNAME [file type] – excel, .txt. Csv, etc LIBNAME PCFILES PROC EXPORT DBMS=[file type] ODS [file type] PROC EXPORT DBMS=[file type] ODS TAGSETS.CSV DATA step, using FILE and PUT to create delimited files ODS TAGSETS.EXCELXP FILENAME DDE SAS Add-In for Microsoft Office   And considering that every run goes through SAS Metadata Manager, would it be possible to contain the data extraction run?   There is sensitive data, strategic business data, as well as the issue of data viewing permission and access, according to the rules and permissions that the user is inserted.   We still have to consider the home office and ensure that this data is not downloaded and used inappropriately. VDI access takes care of some of this, for sure.   However, seeking to ensure that the user gets an error when running a PROC EXPORT would give the company a greater sense of security and compliance.     ... View more