BookmarkSubscribeRSS Feed
KC_Chan
Calcite | Level 5

A libname X to  ODBC statetement with Authdomain parameter is being used in  a Test environment in Di_Studio 4.6.

Libref contains tables with high-confidential data.

In Acceptance enviroment Di_studio  the Libname X is still visible for developers.

The libname definition X will  be secured.

 

However, the definition may still be derived by SAS  developer using naming conventions. Once the Authdomain parameter is known, the developer can have to the table. Also the SAS  log (which can be protected) may show the libname statement also.

The administrator (SAS) only should create/modify the libname in Acceptanace.

 

Are there best pratices within  SAS  to prevent a developer using a Libname with the appropriate to access the tables in Production?

 

Thank you for suggestions.           

1 REPLY 1
LinusH
Tourmaline | Level 20
You can't base security on having a secret syntax!
Protect the data at the source - hence a login from an unathorized user will be rejected or data that is not for him/her to see will not be visible.
Data never sleeps

sas-innovate-2026-white.png



April 27 – 30 | Gaylord Texan | Grapevine, Texas

Registration is open

Walk in ready to learn. Walk out ready to deliver. This is the data and AI conference you can't afford to miss.
Register now and lock in 2025 pricing—just $495!

Register now

How to connect to databases in SAS Viya

Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 955 views
  • 1 like
  • 2 in conversation