Chat now with support
Chat with Support

Safeguard for Sudo 2.0 - Administrators Guide

One Identity Privileged Access Suite for Unix Introducing Privilege Manager for Unix Introducing Privilege Manager for Sudo Planning Deployment Installation and Configuration
Download Privilege Manager for Unix Software Packages Download Privilege Manager for Sudo Software Packages Quick Start and Evaluation Configure a Primary Policy Server Configure a Secondary Policy Server Install PM Agent or Sudo Plugin on a Remote Host Remove Configurations
Upgrading Privilege Manager System Administration Managing Security Policy The Privilege Manager for Unix Security Policy Advanced Privilege Manager for Unix Configuration Administering Log and Keystroke Files InTrust Plug-in for Privilege Manager Troubleshooting Privilege Manager for Unix Policy File Components Privilege Manager Variables Privilege Manager for Unix Flow Control Statements Privilege Manager for Unix Built-in Functions and Procedures Privilege Manager Programs Installation Packages Unsupported Sudo Options Sudo Plugin Policy Evaluation About us

How Privilege Manager for Unix Protects

Introducing Privilege Manager for Unix > How Privilege Manager for Unix Protects

Privilege Manager for Unix protects your systems by:

  • partitioning root (and other important account) functionality to allow many different users to carry out system administration tasks
  • creating an indelible audit trail of these administration tasks

Partition root Safely

Introducing Privilege Manager for Unix > How Privilege Manager for Unix Protects > Partition root Safely

The ability to partition system administration actions without compromising the security of the root account is an extremely powerful one. Privilege Manager for Unix allows you, the system administrator, to set policies to determine whether and when a user request to run a program is accepted or rejected.

Through Privilege Manager for Unix, each user can request that a specific program is run on a specific machine as root (or as another important account such as oracle or admin). Privilege Manager for Unix evaluates the request; if accepted, it runs the program, locally or across a network, on behalf of the user.

With Privilege Manager for Unix, Helpdesk personnel can replace passwords for users or reinstate user accounts. Project members can clear a jammed line printer queue, kill hung programs, or reboot certain machines. Administration staff can print or delete resource usage logs or start backups.

Through partitioning, Privilege Manager for Unix allows different users to perform the root actions for which they are responsible, but prevents them from performing actions for which they do not have authorization.

Privilege Manager for Unix lets you specify:

  • which user(s) can perform a particular task
  • which tasks can be run through the system
  • when the user can perform the task
  • which machine can perform a task
  • from which machine the user may initiate a request to perform the task
  • whether another user’s permission (in the form of a password) is required before the task is started
  • decisions to be made by a program that you supply, which Privilege Manager for Unix calls to determine if a request should be accepted or rejected
  • many other miscellaneous properties of requests

Create an Indelible Audit Trail

Introducing Privilege Manager for Unix > How Privilege Manager for Unix Protects > Create an Indelible Audit Trail

Privilege Manager for Unix can record all activity which passes through it, down to the keystroke level. The power to accurately log root and other account activities in a safe environment allows you to implement a secure system administration regime with an indelible audit trail. You always know exactly what is happening in root, as well as who did it, when it happened and where.

Since root can modify any file, you must ensure that Privilege Manager for Unix logs are indelible. You can configure Privilege Manager for Unix to receive user requests from the submitting machine, execute tasks on the execution machine, and log all activities on a third, very secure machine (see the illustration in How Privilege Manager for Unix Works).

You can make the machine containing the log files physically inaccessible to users and isolated from remote login over the network. In addition, you can print the logs to hard copy on a secure printer or recorded to a WORM drive.

You can also assign this secure machine a root password which is unknown to the person who has physical access to it, but known to someone else without physical access. Two people would have to conspire to subvert system security.

You may use these and other techniques to achieve a high degree of security around Privilege Manager for Unix itself, as well as the logs of root activity that it creates.

Encryption

Introducing Privilege Manager for Unix > How Privilege Manager for Unix Protects > Encryption

You can encrypt all communication among Privilege Manager for Unix programs, and between the user and the application he is running to guard against network snooping or spoofing.

Privilege Manager for Unix supports the following encryption algorithms:

  • AES
  • Kerberos
  • TripleDES and DES

Set the encryption method in the /etc/opt/quest/qpm4u/pm.settings file. (See the encryption setting in PM Settings Variables for details.)

Related Documents