How data is protected
- User passwords are never stored, only as a salted hash (scrypt).
- Server passwords are stored encrypted in the database (Fernet/AES). The key is derived from the master password (scrypt, with a random salt in the database). Without the master password the passwords are unreadable, even for a database administrator.
- Access rights are checked in the program logic on every connection attempt.
- Approvals are time-limited. After expiry a new request is needed.
- The master password is optionally stored in the Windows vault of the signed-in Windows user.
Log
The database (table “audit_log”) records with timestamp and user name: sign-ins (including failed ones), requests, approvals, rejections, connections and changes to resources. The log can be read by a database query. There is no display in the program yet.
Known limitations
Please take these points into account:
- RDP: While the connection is being made, the password briefly appears in the command line of the Windows helper cmdkey and is visible to local administrators of this PC.
- SSH: The password sits on the clipboard for 30 seconds.
- Whoever gets access can technically see the password during the connection. The system controls who may connect; it does not prevent the user from passing it on.
- An expiring approval does not end running sessions, it only blocks new connections.
- No two-factor sign-in, no Active Directory or LDAP integration.
- The master password cannot be reset.
- The installer is not code-signed.
Recommendations for operation
- Create at least two admin accounts.
- Keep the master password separate and safe, e.g. in a password vault.
- With PostgreSQL: use a dedicated database user, allow access only from the company network and back up the database regularly.
- Use a separate service account with minimal rights per server.
- Grant approvals as short as necessary.
What the Free edition does not include
- No assignment of resources to individual users or groups; access is controlled per resource.
- No display of the log in the program.
- No Active Directory or LDAP integration, no single sign-on, no two-factor sign-in.
- No session recording: connections run through the Windows programs mstsc (RDP) and OpenSSH (SSH).
- Windows only, no web or mobile version.