BookmarkSubscribeRSS Feed

Proven Practices for Managing the Enterprise Administrators of a SAS Software Deployment

Started ‎02-29-2016 by
Modified ‎03-02-2016 by
Views 923

There can be a need to provide multiple administrators with the ability to manage your software. The rationale will span from separation of roles and responsibilities (for example, installer and configuration manager) to changing job responsibilities or even just providing coverage while the primary administrator is on vacation. To meet that need, it’s tempting to share the logon credentials of your SAS installer account, but doing so can potentially compromise your security and fail a corporate audit.

 

The SAS Installer user ID on a UNIX (or Linux) system is typically named something generic, such as "sas" or "sasinst." That account, like others associated with SAS and other software services, is often not tied to any single person in the enterprise. The role of SAS Administrator could be a job function of one or several people – over time or at any point in time – as professionals follow their careers.

 

This paper focuses on a basic IT practice and utility to help you diligently manage the administration of your SAS software, while properly ensuring that access is secured and auditability is maintained.

Version history
Last update:
‎03-02-2016 09:59 AM
Updated by:
Contributors

SAS Innovate 2025: Call for Content

Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!

Submit your idea!

Free course: Data Literacy Essentials

Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning  and boost your career prospects.

Get Started

Article Tags