When you have a set of two or more Safeguard for Privileged Sessions (SPS instances in your deployment, you can join them into a cluster. This has several advantages. You can:
Manage the nodes from one central location.
Monitor their status and update their configuration centrally.
Search all session data recorded by all nodes in the cluster on a single node.
Scale the performance of the cluster by adding new nodes and joining them to the cluster easily.
Extend auditing to other networks by adding new nodes to the cluster and joining them to the cluster.
This is achieved by assigning roles to the individual nodes in your cluster: you can set one of your Safeguard for Privileged Sessions nodes to be the Central Management node and the rest of the nodes are managed from this central node.
|
NOTE:
All nodes in a cluster must run the same version of SPS. |
|
NOTE:
One Identity recommends managing not more than a few tens of instances from the Central Management node. |
Nodes in the cluster connect to each other using IPsec.
Assigning roles to nodes in your cluster
Configuration synchronization across nodes in a cluster
Configuration synchronization and SSH keys
Using a configuration synchronization plugin
Monitoring the status of nodes in your cluster
Updating the IP address of a node in a cluster
Managing a cluster with configuration synchronization without central search
Managing a cluster with central search configuration and configuration synchronization
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center