Security optimization
Relution is a powerful tool with which users sometimes have extensive authorisations on managed devices. The system should therefore be optimally protected against unauthorised access. The Relution portal can be optimised in terms of security at various points with built-in functions. Added to this is the targeted distribution of necessary authorisations.
Use a secure password
When a user account is created, the dialog shows a password under Generate example password that complies with the organization’s password policy. It can be copied to the clipboard and pasted into the password fields, or regenerated with Generate. In any case, the password should comply with the complexity recommendation of the BSI →.
Which passwords Relution accepts is defined by the password policy of each organization under Settings → Login Management, among others via Minimum password length (default: 8 characters) and Maximum password age in days (default: 0, passwords do not expire). Disable forgot password reset turns off resetting the password by email. Details under Login Management →.
Add a second factor for authentication
Relution supports login with a second factor. Users set up the MFA token for their own account at the top right via Username → Profile. A token for an authenticator app or email verification can be stored there. Which methods are available is defined under Settings → Login Management.
MFA becomes mandatory through a custom permission with the option Enforce multi-factor authentication for the role, which is assigned to users or groups. Users without a token then have to set one up at their next login. Since the default roles cannot be edited, a custom role is created for this. Using this function is strongly recommended. Details under Multi-factor authentication →.
Use access token
In Relution, an access token for using the API can also be stored in the user account profile. This token offers the advantage that no username/password combination needs to be stored in plain text in scripts. As of Relution 26.5.5, HTTP Basic authentication for the API is disabled by default; scripts therefore authenticate with an access token.
As of Relution 26.5.5, every API token has an expiration date. When a token is created, the Expiration Date field is pre-filled with the default lifetime, 30 days in the future by default. As of Relution 27.0.1, Relution additionally limits the lifetime to a maximum of 1 year from creation; the dialog shows the latest possible expiration date. A shorter limit can be enforced on the server via relution.security.access-token.max-lifetime (environment variable RELUTION_SECURITY_ACCESSTOKEN_MAXLIFETIME), e.g. 90d. The value must not be lower than the default lifetime relution.security.access-token.default-lifetime, otherwise the server does not start. Existing tokens keep their expiration date. The validity period should not be longer than the token is actually needed. The expiration date cannot be changed afterwards: before it expires, a new token is created and replaced in the script. API tokens that were created without an expiration date before the update expire 30 days after the update and must be replaced by then if they are still needed. Details on validity and configuration can be found under REST API →.
Configuring IP Access Rules & Fail2Ban
In the global organization, both IP access rules and Fail2Ban can be configured underSettings → System Security.
IP blocking and the IP access rules only take effect if the Enabled toggle is switched on in the General section (default: off).
This allows defining, for example, that an IP address is blocked after a certain number of failed login attempts and whether the block is lifted automatically after a set time. An IP address is blocked as soon as its failed attempts exceed Maximum failed logins, so with the default value of 10 on the eleventh failed attempt.
IP access rules generally control from which IP addresses or networks a login is allowed or blocked. Both single IPs and entire ranges can be defined. The rules and IP blocking apply to logins with username and password. Logins via single sign-on (SAML/OIDC) and API access with an access token are not checked against the IP access rules. Existing sessions are not affected by new rules.
If Relution runs behind a reverse proxy, the proxy has to pass on the client’s IP address in the X-Forwarded-For header. Otherwise, all logins appear with the proxy’s IP address: IP blocking then blocks the proxy and thus all users, and rules for individual client addresses do not take effect.
In addition to IP blocking, a user account can be deactivated after repeated failed attempts for each organization under Settings → Login Management (User deactivation on failed consecutive login attempts, default: off; Maximum failed login attempts, default: 10). Details under IP block after failed logins →.
Meaning of status values
Allowed
- Login is currently possible
- Is created automatically as soon as a login with invalid credentials fails from an IP address, and counts the failed attempts
- If the number of failed attempts exceeds Maximum failed logins, the status changes to Blocked
- A successful login from this IP address removes the entry
- Cannot be assigned manually
Permanently allowed
- IP address is explicitly whitelisted
- Takes precedence over other rules
- Remains permanently active
- Recommended for trusted locations (e.g. office or VPN)
Blocked
- IP address is blocked. If Clear blocked IP addresses after specified time is enabled (default: off), the entry is deleted automatically after the time set under Clear blocked after (in minutes) (default: 60), which lifts the block. Otherwise, the block remains until the entry is removed manually or the IP address is allowed.
- Can be unblocked at any time
Permanently blocked
- IP address is permanently blocked
- No login possible anymore
- Useful for clearly unwanted access attempts
Use of IP ranges
The so-called CIDR prefix defines how large the IP range is that a rule applies to.
| Prefix | Meaning |
|---|---|
/32 | Exactly one single IP address |
/24 | A typical network (e.g. company network) |
Basic rule:
The smaller the number, the larger the covered IP range.
CIDR examples
192.168.1.10/32
→ Affects exactly one single device192.168.1.0/24
→ Affects all devices from192.168.1.1to192.168.1.254
Define trusted IPs
- Own or known networks are defined.
- These are configured as Permanently allowed.
- Examples:
- Office network
- VPN access
Create global block rule
- A rule is created covering all remaining IP addresses.
- Example:
0.0.0.0/0(covers all IPs worldwide) - Status: Permanently blocked
- The rule only blocks logins with username and password, not single sign-on or API access with an access token.
Security optimizations for enrollments
The link and QR code of an enrollment act like an access key: as long as the enrollment is valid, it can be used to enroll a device in Relution. The device then receives the policies and rulesets linked to the enrollment – which may include Wi-Fi credentials, certificates or access to company services. Open enrollments should therefore be kept to a minimum.
- Keep the validity short: When an enrollment is created, Valid until is set to seven days in the future by default. The period should not be longer than actually required for the planned enrollment. If the time is not sufficient, enrollments that have not yet been used can be extended later via Extend Enrollments – long validity periods as a precaution are therefore not necessary. The field is not mandatory: if it is left empty, the enrollment is valid indefinitely.
- Prefer single-use enrollments: By default, each enrollment can only be used for a single device. A Multi-use enrollment, on the other hand, allows any number of devices to be enrolled until the expiration date, limited only by the available licenses. It should therefore only be used specifically for larger rollouts and combined with a particularly short validity.
- Delete enrollments that are no longer needed: Open enrollments that are no longer required – for example after a rollout has been completed or if a device is not enrolled after all – should be deleted under
Devices→Enrollments. Devices that have already been enrolled via a multi-use enrollment remain enrolled. For Android Enterprise, the associated enrollment token is also deleted at Google, so the QR code no longer works. - Do not share links and QR codes publicly: Enrollment links are only sent to the intended recipients and are not published on the intranet, in wikis or via large mailing lists. Printed QR codes are destroyed after the rollout.
- Review enrollments regularly: The list under
Devices→Enrollmentsshows, based on the Status and Expiration date columns, which enrollments are still open. In addition, the device inventory should be checked for unexpected devices. - Short links: As of Relution 26.5.4, enrollment short links are at least 12 characters long (previously 7 by default). The length can be increased via
relution.enrollment.short-code-lengthin theapplication.yml; the server raises smaller values to 12 and logs a warning. A short link only redirects to open enrollments that have not expired. Once the device is enrolled or the enrollment has been deleted or has expired, the short link no longer works. Short links of open enrollments that have already been sent remain valid. - macOS: profile removal password: For macOS enrollments, Use profile removal password can be enabled. The MDM profile can then only be removed from the device with an automatically generated password.
Manage permissions
Relution offers twelve authorisation preconfigurations as standard. It is advisable to check which functions are active in which authorisation preset. For this purpose, the entries created by the system are reviewed under Users → Permissions. These roles cannot be edited. However, new authorisations can be created at any time, enabling the necessary functions for individual users on a fine-grained basis.
The authorisations correlate with the user groups created by Relution. Details under Permissions →.