BI Tools

Tips and tricks for building information maps, OLAP cubes, reports, and dashboards

BI Admin

Learn your way around a SAS BI installation.

Visual Analytics

Learn your way around the SAS Visual Analytics tool

Coding & Data

Extract, transform, and load your data into the SAS BI toolset

Stored Processes

Create and design stored processes like a rock star

Home » Enterprise Guide

SAS Enterprise Guide: Shielding your EG project from Hound Dogs

Submitted by on 2011-11-21 – 6:32 AM 11 Comments

Harsh Gajjar is SAS Business Intelligence (BI) and SAS Design Integration (DI) rising star in India. Today he is discussing how to keep nosy co-workers (lovingly referrer to as hound dogs) from disturbing your code or when you want to ensure changes are not made by accident to your neat, sweet, and complete SAS Enterprise Guide projects.

Post Author: Harsh Gajjar 

Securing SAS Enterprise Guide Projects 

Every BI professional must be acquainted with the SAS Enterprise Guide Project. However here I’m going to discuss about the issues related to securing your process flow from unauthorized access. We are quite aware of the fact that the metadata security and permissions enable a user to restrict the access of data to specific people. (viz. SAS Admin ). However the metadata does not restrict a person from peeking into someone’s process flow or project to get some idea.

Use Built-In Password Protection

SAS Enterprise Guide 4.2  has availed a facility to restrict the access to Project through password Protection.

sas enterprise guide secure project

Click on project Properties-> Security and type the desired password. Another window appears to verify your Password. Then Save the Project. Now if  anybody opens the project.egp file in SAS EG then the following window appears:

sas enterprise guide secure project

 Thus in this way one can ensure that their programming logic and methodology are secured and restricted.

Similar kind of strategey employed in case of BASE SAS foundation 9.2. Here read = xxxx and alter = xx  renders restriction on reading and altering the datasets.

sas enterprise guide secure project

 

This was my first post in  SAS business Intelligence World.  Leave some comments below if you have some questions.

Never miss a BI Notes post!

Click here for free subscription. Once you subscribe you'll be asked to confirm your subscription through your email account. You email address is kept private and you can unsubscribe anytime.

Tags:

11 Comments »

  • Harsh Gajjar says:

    @Maye.. Your Welcome.. I’m looking forward for queries and doubt’s related to this topic.

  • Maye says:

    I would really like to give thanks very much for the work you have made in writing this article. I am hoping the same perfect job by you in the future also.

  • Roger Chong says:

    It depends on the department and the team leader. I work for a large financial institution. I password protect my datasets.

  • Harsh Gajjar says:

    @William Thong .. Well certainly.. here we are comparing the stored process and Project.. A stored process is a SAS program that is stored on a server and can be executed as required by requesting applications… So certainly. they are reusable. In order to reuse the project one has to make sure the password is sent to the user.
    Moreover in case of Scheduling the project. we have to manually enter the password. So I would rather say we cannot schedule the password protected project.
    and as @chris said.. u will also have to protect the script.

  • You can automate/schedule a project with a password…but of course, it requires that you specify the password in your automation script. So you must then also protect your script from unauthorized viewers.

    The Application.Open() method (in the automation model) accepts two arguments: the project file name and a password. For more on automation, see: http://blogs.sas.com/content/sasdummy/tag/automation/

  • William Thong says:

    if you password protect a SAS EG project, how would we then create re-usable projects for other users to use? Stored Processes? How do we schedule and run a password protected SAS EG Project?

  • Harsh Gajjar says:

    @daveG.. Yes Putting up a password for a project..may not be an appropriate or we can say completely substandard solution in a company. But here I’m just trying to point out a situation which I’ve observed personally ,since process flow is the concept which is your design on how you are executing your logic in order to transform your data into relevant information. And yes password protection ensures the security of that Process flow from unauthorized access.

    @daveG… Regarding version control .. Then as Tricia Mentioned there have been changes in SAS Enterprise Guide 4.3.. which renders a better version control support.

  • Tricia says:

    Great tips Chris!

  • Tricia says:

    What I love the most about SAS is how many different ways it can be used. You make some excellent points about how source code and datasets would be treated in a production environment.

    This technique is one I would use during the development process. Since not all organizations have version control systems for their code, this would give a little insulation from mistakes or accidents. Many times, I find I need to protect the data and project from myself! And I have had circumstances where co-workers have “stepped” on my code or overwritten my dataset by accident.

    Many of the organizations where I have worked the source code control was up to the individual developers. It depends on the size, budget and maturity of the organization. Is that a best practice? No. Does it happen? More than we like to think.

    SAS EG 4.3 supports version control systems. Read more here: http://support.sas.com/resources/papers/proceedings10/137-2010.pdf

    Thanks for your comments! Please keep the feedback coming!

  • daveG says:

    Isn’t this functionality what source control does better and safer.
    At all the companies I have worked with SAS at password protected datasets are banned, in capital letters, and bold, because of the impossibility of ensuring the passwords are kept and given to future users.
    For example when a dataset migration is done in three years…

    Also how can anyone peer- review this code if it is password protected?

    If EG does not support version control I do not see how it is a tool for professionals.

  • This is a great tip/reminder. Actually, the ability to protect a project with a password has been in EG for many releases, at least going back to EG 2.0 (and perhaps earlier).

    DO NOT FORGET YOUR PASSWORD! If you lose the password for a project, not even SAS Technical Support can help you to recover it. As a best practice, it’s a good idea to keep a non-PW-protected version in a safe place.