Date: Tue, 9 Mar 1999 07:18:00 +1100
Reply-To: Tim Churches <email@example.com>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Tim Churches <tchur@BIGPOND.COM>
Subject: Re: Security of a SAS dataset
Content-Type: text/plain; charset="iso-8859-1"
Bernard Tremblay writes:
> SAS doen't offer security on a field basis. But you could achieve it
>by different ways... First, you could put public data and private data
>in two different datasets and have a common unique key that would allow
>an sql view to show the file as one unique file. The second dataset
>would be password protected or encrypted to protect it. SAS would ask for
>the password whenever someone wants to read/write the file with an sql view
>or with a SAS proc.
Yes, we do this all the time although we use operating system security to
control access to the directories (libraries) containing the "private"
portion of the datasets, rather than SAS encryption and dataset passwords.
Works a treat.
I believe that SI's Scalable Performance Data Server (SPDS) product offers
column (variable, field) level security on a per user or group basis. You'll
need deep pockets, though.
>>>>From: Portfolio Information Corporation <portfolio.info@SNET.NET>
>>>>Subject: Re: Security of a SAS dataset
>>>> Does anyone know whether certain fields of a dataset could be
>>>>for access (e.g.. read only with a password or hide) while rest of the
>>>>dataset is accessible. To explain this further, can we hide or restrict
>>>>access to certain sensitive information such as SSN or Mother's maiden
>>>>etc. in a bank dataset, by applying a password access to these fields?
>>>>please reply to: firstname.lastname@example.org