SAS administrators have a delicate balance to maintain. SAS users want to be happy and productive, and to be granted the freedom to use any techniques in their skill set to accomplish their work. But the Business (or Government or Research institution) wants their sensitive data to be protected, and
In the movie, The Matrix: Reloaded, our heroes and the KeyMaker frantically navigated from world to world through a series of doors and locks trying to escape the villains. Fortunately for our heroes, the KeyMaker always had the right key on his ring, he just had to know what key
SHA256 and other hash functions are supported in SAS 9.4 and SAS Viya. It's better than MD5 as a cryptographic hash!
If you’re not an expert on encryption, have no fear! SAS 9.4 has introduced ways to bring stronger encryption to your SAS deployment. The good news is that SAS/SECURE is now a part of Base SAS when you upgrade to SAS 9.4 and is not a separately licensed product anymore.
I love tables. As a writer, there's nothing more satisfying to me than distilling complicated information into neat rows and columns. That's one of the features that caught my eye in SAS User ID and Password Usage Rules. The other is its potential usefulness for SAS administrators who manage SAS
Reading Jan Bigalke’s SAS Global Forum paper on “Hardening a SAS® Installation on a multi tier installation on Linux" reminded me of baking apple stack cake with my mother. Neither is a simple project. Both are time-consuming, and their success depends on how skillfully you handle each layer. Data security
Many people mistakenly assume that just because you want to use a SAS program to access a protected resource (such as a database table), you must include the credentials for the resource inside your program. Few things cause a database administrator to lose more sleep than coming across this within
