Skip to main content

How to get information about user activity on SAS server?

Question:
We need to collect user activity some information and turn them as a report in SAS. We are expecting report such as when a user connect to sas dataset, name of the table user accessed and changes made to the user on that table?

Answer:
SAS by default provides several ways to audit the access to its components. This question in about SAS Dataset components (ie) access to the data.

This requirement is more popular as SAS are widely used in banking, clinical where the data access needs to be audited.

To achieve the report that you are looking for you can check SAS Logging Facility. There are several options which you can enable in the Workspace server or any other SAS servers. This options will allow you to customise the way you want.

Genrally, a good option is that if you have middle tier in your deployments, is to enable the EMI framework and then set up the Audit Performance and Measurement (APM) tools (optionally, also ARM for performance monitoring, and VAfeed, to load the data into your VA or VAAR web application). 

You can find more information in the below link:
https://support.sas.com/rnd/emi/SASEnvMgr/EVSAF/index.html

At last, I would say that one of the best options is to purchase and configure the SAS Federation Server, which allows you to monitor and audit every single action on the data, plus you can control the authorisations (and row-level security) and the way users access the data (anonymity, encryption, masking, etc)

If you are looking for more tailor made solution it is best to contact SAS representative.

Comments

Popular posts from this blog

Starting Gemfire in SAS

Gemfire is available in both Compute and Mid. The default port is 41415. If you have many gemfire, you may have port numbers incremented by 1, for example: 41416. Gemfire is located under Web. <SASCONFIG>/Web/gemfire. To Start: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh start To check Status: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh status To stop: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh stop If it doesn;t start check port number is occupied by any other process. lsof -i tcp:41415 If you only have one instance then 41415 will be default. If you have Lev2 then it will be 41416

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...