Chat now with support
Chat with Support

Safeguard for Sudo 7.0 - Release Notes

System requirements

Before installing Safeguard 7.0, ensure that your system meets the following minimum hardware and software requirements.

NOTE: Beginning with version 7.0, Safeguard for Sudo supports only Linux-based systems for Safeguard policy servers.

Table 3: Hardware and software requirements
Component Requirements
Operating systems

See Supported platforms to review a list of platforms that support Safeguard clients.

Disk space

80 MB of disk space for program binaries and manuals for each architecture.


  • At a minimum, you must have 80 MB of free disk space. The directories in which the binaries are installed must have sufficient disk space available on a local disk drive rather than a network drive. Before you install Safeguard, ensure that the partitions that will contain /opt/quest have sufficient space available.
  • Sufficient space for the keystroke logs, application logs, and event logs. The size of this space depends on the number of servers, the number of commands, and the number of policies configured.

  • The space can be on a network disk drive rather than a local drive.

  • The server hosting Safeguard must be a separate machine dedicated to running the pmmasterd daemon.
SSH software

You must install and configure SSH client and server software on all policy server hosts.

You must also install SSH client software on all hosts that will use the Sudo Plugin.

You must enable access to SSH as the root user on the policy server hosts during configuration of the policy servers. Both OpenSSH 4.3 (and later) and Tectia SSH 6.4 (and later) are supported.

Processor Policy Servers: 4 cores
Policy Servers: 4GB
Table 4: Primary policy server and host system installation requirements
Systems Required Minimum Requirements
Primary Policy Server

  • Supported Unix or Linux operating system
  • SSH (ssh-keyscan binary)

  • Supported Unix, Linux, or macOS platform
  • SSH (ssh-keyscan binary)
  • Sudo 1.8.1 (or later)

Upgrade and compatibility

Safeguard for Sudo supports a direct upgrade installation from versions 2.0 and higher. The Safeguard software in this release is provided using platform-specific installation packages. For more information on upgrading, see the One Identity Safeguard for Sudo Administration Guide.

One Identity recommends that:

  • You upgrade your policy server (Master) systems before Sudo plugins, and that a policy server is run at the same or higher level than Sudo plugins.
  • All policy server systems and Sudo plugins are upgraded to the latest version to take advantage of all new features.

The upgrade process will create symbolic links to ensure that your existing paths function correctly.

Product licensing

Although licenses are allocated on a per-agent basis, you install licenses on Safeguard policy servers.

No special commands are required to register or license the clients with policy servers. Hosts using the Safeguard agents are automatically granted a license once a request is received on the Safeguard policy server by means of the sudo client program.

To install a license file

  1. Copy the .dlv license file to the policy server.
  2. To install the license, run:
    # /opt/quest/sbin/pmlicense –l <license_file>

    This command displays your currently installed license and the details of the new license to be installed.

  3. When it asks, "Would you like to install the new license (Y/N) [Y]?", press Enter, or type: Y
  4. If there are other policy servers configured in your policy server group, it forwards the license configuration to the other servers.

See the One Identity Safeguard for Sudo Administration Guide for more information about the syntax and usage of the pmlicense command.

Installation instructions

One Identity recommends that you follow these steps:

  1. Install Authentication Services on one machine, so you can set up your Active Directory forest.
  2. Install One Identity Management Console for Unix, so you can perform all the other installation steps from the management console.
  3. Add and profile hosts using the management console.
  4. Configure the console to use Active Directory.
  5. Deploy client software to remote hosts.
  6. Deploy the Safeguard for Sudo software.

Refer to the Getting Started tab in the management console for a better understanding of the steps to take to be up and running quickly.

More resources

Additional information is available from the following:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating