Security Settings
Manage administrator access, SSH settings, system updates and API access.
Where to find it: Server > Configuration > Security Settings.
Available to: Root only.
What this page does
Use the dedicated groups for root password changes, automatic/manual OS updates, SSH port and permitted users, source-IP access, and Engine API administration. These controls have different scopes and should be changed separately.
Before you start
Keep a working SSH session before changing SSH port, allowed users, or IP access restrictions. Ensure the firewall permits the intended management port before ending the current session.
Provider security controls
| Control | Effect and check |
|---|---|
| Root Password | Set and confirm the new password; verify a new sign-in before closing the current session. |
| Daily Auto Update | Choose the operating-system package update policy and whether kernel packages are excluded. This is separate from the SHM Version page. |
| Update now | Run the offered OS update workflow and inspect its result. |
| SSH Port and SSH AllowUsers | Change the daemon’s management port and allowed SSH users deliberately; test a new connection. |
| IP Access Control | Allow intended management sources and review their public/NAT addresses. |
| Engine API | Manage the intended API identity, roles, enablement, and key operation; verify a role-scoped read after changing an integration key. |
How to use it
- Open the group that owns the intended change.
- Review its current values and recovery path.
- Save one change at a time.
- Test a new login or API request through the changed access path.
Result and next check
The intended access works and the old or excluded access behaves as expected. Web, mail, and FTP client policies have separate account-level controls.
Theme color