The administrators 'root' and 'security'

The administrators root and security are responsible for managing the security system of TightGate-Pro. They can make changes to the security models or provide log analyses for maintenance. However, they are not required for the normal operation and configuration of TightGate-Pro.

For the administrators root and security to log on to TightGate-Pro, an additional activation by the administrator maint is necessary. There is also a time limit; after one hour, the login option via SSH is automatically deactivated and must be reactivated if necessary.

Warning: Improper changes to the security system of TightGate-Pro harbour considerable security risks for the internal network and the workstations on it. Furthermore, serious disruptions to productive operation can occur.

Warning: Customer service operations of m-privacy GmbH that are carried out against the background of improper interventions via the administrators root and security are not covered by the software maintenance contracts. This also applies in particular to any consequential damage, for example due to insufficient protection as a result of an impairment of the security mechanisms of TightGate-Pro.

The role security role defines the possibilities of a security officer and can edit the entire RSBAC set of rules. New roles can be defined and the rights of existing roles can be changed. Due to the scope of authorisation, the role of security is only accessible from the local console by default. SSH access for the administrator security can only be granted by the administrator maint for a limited period of time. To view the status of the security models and the RSBAC rules, it is necessary to log in as administrator security on the console.

The following setting options are available:

The role root role essentially corresponds to that of the classic administrator for system services. As administrator root administrator, installed system services can be started and stopped, tests can be carried out with system tools and system services can be configured. In contrast to the administrator account of a conventional Linux system with the same name and unlimited authorisation, the role of root role is subject to special restrictions. For example, the administrator root administrator cannot access user directories, assign RSBAC rights to programmes or change RSBAC rights, but can view them.

To display the status of the security models and processes and to view the current system log, it is necessary to log in as administrator root on the console is required.