Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Privilege Manager for Unix 6.1.1 - Administration Guide for Unix

One Identity Privileged Access Suite for Unix Introducing Privilege Manager for Unix Planning Deployment Installation and Configuration Upgrade Privilege Manager for Unix 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

Medium business deployment

The medium business model is suitable for small organizations with relatively few hosts to protect, all of which may be located within a single data center.

This configuration example comprises multiple UNIX/Linux hosts located within the SME space and one or more web servers located in a DMZ.

The tunneling feature (pmtunneld), enables Privilege Manager for Unix to control privileged commands on the web servers across a firewall, within the DMZ. This configuration significantly reduces the number of open ports at the firewall.

Multiple policy server components (pmmasterd) are installed in a failover configuration, with groups of agents balanced between the policy servers. If a policy server is unavailable for any reason, the agents will failover to the alternative policy server.

Figure 4: Medium business implementation: Minimum 2 Masters and Circa 100 Agents

Large business deployment

This is an example of how a large business might deploy Privilege Manager. Some global companies prefer to fragment their requirement and deploy multiple instances as shown in the medium-sized business model.

This example comprises three policy servers, two are balancing the load of multiple agents. This may be necessary if there is a high level of audit and/or a significant volume of requested elevated privilege. Further, there is an additional policy server configured as a failover should one or both policy servers become unavailable.

Figure 5: Large business implementation: Minimum 3 Masters and less than 1000 Agents

Enterprise deployment

This example is based on an organization with offices in London and New York. Again, as with the medium-sized business example, the web servers and corporate web-based applications reside in a DMZ. The requirement to run commands at an elevated level from inside the firewall remains.

Access to the web server and web applications is predominantly, but not exclusively, from the London office. Privilege Manager for Unix tunnelling components are used to breach the firewall to the DMZ.

In addition, internal firewalls are located between the offices in London and New York, and tunneling components are deployed to enable access from office to office and indeed from anywhere to the DMZ.

Within each office, multiple policy servers are configured for load balancing, with each policy server serving a number of agents.

Figure 6: Enterprise deployment implementation: Minimum 4 Masters and 1000 Agents and above

You can extend each of the models described above by, for example, adding more policy servers, configuring additional load balancing, assigning dedicated audit, logging and reporting servers. The models provide a small indication of the flexibility and modular way in which you can configure and implement Privilege Manager to meet the precise requirements of any size business.

Installation and Configuration

This is an overview of the steps necessary to set up your environment to use Privilege Manager software:

To configure a primary policy server

  1. Check the server for installation readiness.
  2. Install the Privilege Manager policy server package.
  3. Configure the primary policy server.
  4. Join the primary policy server to policy group.

To configure a secondary policy server

  1. Check the host for installation readiness.
  2. Install the Privilege Manager policy server package.
  3. Configure the secondary policy server.
  4. Join the PM Agent to the secondary policy server.

To install the PM Agent on a remote host

  1. Check the remote host for installation readiness.
  2. Install the Privilege Manager software on the remote host.
  3. Join the PM Agent to the policy server.

The following topics walk you through these steps.

Documents connexes