Whether the user can use their credentials to authenticate to remote devices when starting a session, these devices, or users, must be configured appropriately and segregated with permission to use a personal credential.
In these cases, the Segura™ user can access the device by providing their username, which isn’t registered with Segura™, to the device managed by Segura™.
The proxy system will ask for the password for this personal credential to start the session. This password won’t be stored by Segura™.
For the command audit to be valid for personal credentials, the commands must be registered as global or by the device since the audit occurs through these channels and not through credentials.
Access policy requirement
To open a session with a personal credential through the proxy, the user needs session permission on the device through an access policy. Without this permission, Segura™ refuses the session and the proxy shows one of these messages:
| Proxy | Message |
|---|---|
| Terminal proxy | No access to device. |
| RDP proxy | Access denied to credential. |
Segura™ records each refused session in Session events.