Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Nexus Hybrid Access Gateway - Internal is shipped as a virtual appliance that uses an Ubuntu base image. With every release of Hybrid Access Gateway this base image is hardened in different areas:
- Only installing required software and services
- Restricted user management
- Continuous security updates
Expand | ||
---|---|---|
| ||
During the installation, Hybrid Access Gateway installs the OpenSSH server for communication from outside. A Postgres database is installed and only used for local communication. Connections from outside are disabled by default. During the installation, the default firewall of Ubuntu is applied. Only features that comes by default with the corresponding Ubuntu base image (currently 1418.04) are available within the Hybrid Access Gateway appliance, including:
If Hybrid Access Gateway is configured to use an external database for users, reporting and OATH, the internal Postgres database service can be turned off without any hassle. ImportantTo improve the hardening index of Hybrid Access Gateway, an SSH configuration parameter ( To increase the amount of authentication attempts:
In case of Hybrid Access Gateway upgrades, this change has to be done after the appliance has been upgraded successfully. |
Expand | ||
---|---|---|
| ||
All services in Hybrid Access Gateway are run by a separate user named pwuser. Authentication from outside is not allowed with that user. For authentication from outside, the user agadmin is created during installation. Writing permissions to Hybrid Access Gateway-related files are restricted to power users, such as pwuser and root. Because of security reasons, the passwords of pwuser and root can be changed after installation. To do this, use sudo access of agadmin or root. The pwuser could still not be used to authenticate from outside after this change. All passwords are saved as part of the default location of passwords. Change root password
|
Expand | ||
---|---|---|
| ||
With every release of Hybrid Access Gateway, all binaries are updated to the latest versions to prevent security vulnerabilities as much as possible. Therefore, vulnerabilities like Spectre and Meltdown are taken care off as soon as updates are available. A steady release cycle ensures prompt security updates. |
Expand | ||
---|---|---|
| ||
The communication between Hybrid Access Gateway nodes is secured with a Nexus proprietary protocol called LCP. The protocol is based on length, type and value. LCP uses a shared secret which is initialized during the system setup. Once the secret is shared among all the registered nodes the secret is never shared again. Although, it is possible to update the secret time-to-time for security purpose. To update the secret, use one of the two following methods:
OR
The following types of data are encrypted over LCP:
|
Expand | ||
---|---|---|
| ||
On a regular basis, Nexus instructs specialized, external companies to perform penetration tests on the latest versions of Hybrid Access Gateway, to ensure that it maintains it high security status. Critical vulnerabilities found by PEN testing will be fixed as soon as possible and released with the next version (or an interim version if required). |
This article is valid from Hybrid Access Gateway 5.13.1.