Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Safeguard for Sudo 7.2.3 - Administration Guide

Table of Contents

Introducing Safeguard for Sudo

Features and benefits of Safeguard for Sudo How Safeguard for Sudo works

Planning Deployment

System requirements

Supported platforms Reserve special user and group names Required privileges

Estimating size requirements Safeguard licensing Deployment scenarios

Single host deployment Medium business deployment Large business deployment

Installation and Configuration

Download Safeguard for Sudo software packages Verifying package signature Configure a Primary Policy Server

Checking the server for installation readiness

TCP/IP configuration Hosts database Reserve special user and group names Policy server daemon hosts Check Sudo version

Installing the Safeguard packages

Adding directories to PATH environment

Configuring the Safeguard for Sudo Primary Policy Server

Configuring additional policies on a policy server Safeguard for Sudo Server Configuration Settings

Join hosts to policy group

Joining Sudo Plugin to Policy Server

Joining Sudo Plugin to policy server using a non-default policy

Swap and install keys

Configure a secondary policy server

Installing secondary servers Configuring a secondary server

Synchronizing policy servers within a group

Install Sudo Plugin on a remote host

Checking Sudo Plugin Host for installation readiness Installing a Sudo Plugin on a remote host Joining a Sudo Plugin to a primary policy server Verifying Sudo Plugin configuration Load balancing on the client

Remove configurations

Uninstalling the Safeguard software packages Uninstalling Safeguard for Sudo on macOS

Upgrade Safeguard for Sudo

Before you upgrade Upgrading Safeguard packages

Upgrading the server package Upgrading the Sudo Plugin package

Removing Safeguard packages

Removing the server package Removing the Sudo Plugin package

System Administration

Reporting basic policy server configuration information Checking the status of the master policy Checking the policy server Checking policy server status Checking the Sudo Plugin configuration status Installing licenses

Displaying license usage

Listing policy file revisions Viewing differences between revisions Backup and recovery

Managing Security Policy

Security policy types Specifying security policy type The sudo type policy Viewing the security profile changes Managing policies in Git

Prerequisites for Git policy management Example setup with GitHub

Administering Log and Keystroke Files

Configuring keystroke logging for Safeguard for Sudo policy

Validating Sudo commands

Event logging Keystroke (I/O) logging Sub-command logging

Audit server logging

Configuration options

Viewing the log files using command line tools Listing event logs Backing up and archiving event and keystroke logs

Supported sudo plugins

Configuring a sudo approval plugin Configuring a sudo audit plugin

Troubleshooting

Enabling sudo policy debug logging Enabling tracing for Sudo Plugin Join fails to generate a SSH key for sudo policy Join to policy group failed on Sudo Plugin Load balancing and policy updates Policy servers are failing pmgit Troubleshooting

Setting alert for syntactically incorrect policies Automatic synchronization failed Failed to push references to Git URL

Sudo command is rejected by Safeguard for Sudo Sudo policy is not working properly

Safeguard Variables

Global input variables

argc argv client_parent_pid client_parent_uid client_parent_procname clienthost command cwd date day dayname domainname env false gid group groups host hour masterhost masterversion minute month nice nodename optarg opterr optind optopt optreset optstrictparameters pid pmclient_type pmclient_type_pmrun pmclient_type_sudo pmversion ptyflags requestlocal requestuser rlimit_as rlimit_core rlimit_cpu rlimit_data rlimit_fsize rlimit_locks rlimit_memlock rlimit_nofile rlimit_nproc rlimit_rss rlimit_stack samaccount selinux status submithost submithostip thishost time true ttyname tzname uid umask unameclient uniqueid user year

Global output variables Global event log variables

event exitdate exitstatus exittime

PM settings variables

Safeguard programs

pmauditsrv pmcheck pmgit

pmgit subcommands

pmgit export pmgit Import pmgit Enable pmgit Disable pmgit Update pmgit Set pmgit Status pmgit Help

pmjoin_plugin pmkey pmlicense pmloadcheck pmlog pmlogadm pmlogsearch pmlogsrvd pmlogxfer pmmasterd pmplugininfo pmpluginloadcheck pmpolicy pmpolicyplugin pmpoljoin_plugin pmpolsrvconfig pmremlog pmreplay

Navigating the log file

pmresolvehost pmserviced pmsrvcheck pmsrvconfig pmsrvinfo pmsum pmsysid

Installation Packages

Package locations Installed files and directories

Supported Sudoers directives Unsupported Sudo Options

Unsupported command line sudo options Behavioral change Unsupported Sudoers policy options Unsupported Sudoers directives

Safeguard for Sudo Policy Evaluation

Checking the status of the master policy

System Administration > Checking the status of the master policy

The "master" copy of the policy file resides in a repository on the primary policy server. Each primary and secondary policy server maintains a "production" copy of the policy file or files. Use the pmpolicy utility to verify that the production copy is current with the master policy.

To compare the production policy file against the master policy on the primary server

From the command line, enter:
```
# pmpolicy masterstatus
```
If the files are in sync, the Current Revision number will match the Latest Trunk Revision number. If someone hand-edited the local copy without using pmpolicy utility commands to commit the changes, "Locally modified" will indicate "YES".

If the production policy is not current with the master policy you can update the production policy with pmpolicy sync.

Related Topics

Checking the policy server

System Administration > Checking the policy server

When the policy server is not working as expected, use the pmsrvcheck command to determine the state of the server and its configuration.

To verify the policy server is running

From the command line, enter:
```
# pmsrvcheck
```
This command returns output similar to this:
```
testing policy server [ Pass ]
```
If the policy server is working properly, the output returns 'pass', otherwise it returns, 'fail'.

Related Topics

Checking policy server status

System Administration > Checking policy server status

The primary and secondary policy servers need to communicate with each other. The Sudo Plugin hosts also need to communicate with the policy servers in the policy group. Run pmpluginloadcheck on the remote hosts to verify that they can communicate with the policy servers in the group.

To determine if there any issues with policy servers in the policy group

From the Safeguard for Sudo host command line, enter:

# pmpluginloadcheck -r

This command has output similar to this:

[0][root@sol10-x86 /]# pmpluginloadcheck -r 
** Reporting current availability of each configured master... 
   * Host:myhost1.example.com (172.16.1.129) ... [ OK ] 
** Based on this data, the server list is currently ordered as: 
1.	myhosts.example.com

Related Topics

pmpluginloadcheck

Checking the Sudo Plugin configuration status

System Administration > Checking the Sudo Plugin configuration status

To check the Sudo Plugin configuration status

From the command line, enter:
```
# pmplugininfo
```
This command returns output similar to this:
```
# pmplugininfo 
   - Joined to a policy group          : YES 
   - Name of policy group              : MyPolicyGroup 
   - Hostname of primary policy server : myhost.example.com
```
If the Sudo Plugin has been properly configured, it will say Joined to a Policy Group: YES and give the policy group name and primary policy server’s hostname.

Related Topics

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center