When four-eyes authorization is required for a connection, a user (called authorizer) must authorize the connection on One Identity Safeguard for Privileged Sessions (SPS) as well. This authorization is in addition to any authentication or group membership requirements needed for the user to access the remote server. Any connection can use four-eyes authorization, so it provides a protocol-independent, out-of-band authorization and monitoring method.
The authorizer has the possibility to terminate the connection any time, and also to monitor real-time the events of the authorized connections: SPS can stream the traffic to the Safeguard Desktop Player application, where the authorizer (or a separate auditor) can watch exactly what the user does on the server, just like watching a movie.
The auditor can only see the events if the required decryption keys are available on the host running the Safeguard Desktop Player application.
Figure 16: Four-eyes authorization
Technically, the process of four-eyes authorization is the following:
Four-eyes authorization can be used together with other advanced authentication and authorization techniques like gateway authentication , client- and server-side authentication, and so on.
The user initiates a connection from a client.
If four-eyes authorization is required for the connection, SPS pauses the connection.
The authorizer logs in to the SPS web interface, selects the connection from the list of paused connections, and enables it.
The user performs the authentication on the server.
The auditor (who can be the authorizer, but it is possible to separate the roles) watches the actions of the user real-time.
The One Identity Safeguard for Privileged Sessions (SPS) hardware has five network interfaces: three physical interfaces for handling traffic, the HA interface for communicating with other nodes in a High Availability cluster, and the IPMI interface. The T10 hardware has two additional network interfaces available: the SFP+ interfaces labeled A and B. For details on hardware installation, see "One Identity Safeguard for Privileged Sessions Hardware Installation Guide" in the Installation Guide.
You can assign any number of logical interfaces (alias IP addresses and netmasks) to a physical interface, and each logical interface can have its own VLAN ID. For more information on managing logical interfaces, see Managing logical interfaces.
The routing rules determine which interface is used for transferring remote backups and syslog messages of SPS.
One Identity recommends that you direct backups, syslog and SNMP messages, and e-mail alerts to a dedicated interface. For details, see Configuring the routing table.
The HA interface is an interface reserved for communication between the nodes of SPS clusters. The HA interface uses the Ethernet connector labeled as 4 (or HA). For details on High Availability, see High Availability support in One Identity Safeguard for Privileged Sessions (SPS).
In case of T10 hardware, the SFP+ interfaces are available for both proxy traffic and for local services. This means that these interfaces can be used for the same purposes as the other 3 physical interfaces.
The Intelligent Platform Management Interface (IPMI) interface allows system administrators to monitor system health and to manage SPS events remotely. IPMI operates independently of the operating system of SPS.
High Availability clusters (also called HA clusters) can stretch across long distances, such as nodes across buildings, cities or even continents. The goal of HA clusters is to support enterprise business continuity by providing location-independent load balancing and failover.
In High Availability (HA) mode, two One Identity Safeguard for Privileged Sessions (SPS) units with identical configurations are operating simultaneously. These two units are the primary node and the secondary node (previously also referred to as the master node and the slave node). The primary node shares all data with the secondary node, and if the primary node stops functioning, the other one becomes immediately active, so the servers are continuously accessible.
You can find more information on managing a High Availability SPS cluster in Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster.
One Identity recommends using a High Availability SPS cluster instead of a standalone SPS appliance. A standalone SPS appliance can become a single point of failure (SPOF), and its failure can severely impact your business.
When powering on the One Identity Safeguard for Privileged Sessions (SPS) nodes in High Availability mode, both nodes boot and start the firmware. There is a difference, however, between the two nodes in the services that they start on booting. The secondary node will launch only a few services, those that are required for High Availability support (that is, for awareness of the primary node and data synchronization). The rest of the services (for example, managing connections) start only on the primary node.
Upgrading the SPS firmware via the web interface automatically upgrades the firmware on both nodes.