Support for OpenID Connect (OIDC) by GO-Global enables enterprises and small and medium-sized businesses (SMBs) to deliver single sign-on to their users via OIDC identity providers such as Okta and Active Directory Federated Services (ADFS). For example, it lets users who login into an enterprise web application or portal via an identity provider such as Okta or ADFS to access GO-Global Hosts directly from their browsers without re-entering their credentials.
GO-Global was developed using GraphOn’s proprietary, closed-source RapidX Protocol (RXP). Compared to open-source protocols like Microsoft Remote Desktop Protocol, RXP offers additional defense against attackers simply because it is closed-source.
Two-Factor Authentication (2FA) adds an additional degree of security by asking end users to enter a six-digit code generated by an authenticator app on their smartphone in addition to their username and password. Additionally, 2FA alleviates the difficulty of enforcing a complex password policy.
GO-Global inherits the Windows operating system''s user and data security boundaries, including Group Policies and Access Control Lists. Additionally, GO-Global keeps security settings at the user and application level that are enforced during the logon process.
For all client session connections, GO-Global uses DES (Data Encryption Standard) with a 56-bit key strength to defend against basic packet sniffers and clients eavesdropping raw data transmissions. It is quick and dependable and provides rapid security for LAN-based communications via GO-Global. GO-Global provides TLS-encrypted transport using the following algorithms: 128-bit RC4, 168-bit 3DES, and 256-bit AES. These more robust encryption techniques need the administrator to install a valid TLS certificate on the host, which can be issued using any widely used Certificate Authority. GO-Global provides TLS-encrypted transport using the following algorithms: 128-bit RC4, 168-bit 3DES, and 256-bit AES. These more robust encryption techniques need the administrator to install a valid TLS certificate on the host, which can be issued using any widely used Certificate Authority.