Skip to main content
Security policies limit already-issued capabilities; they work together with roles, grants, projects, local agent policies, and Linux rights; the enabling role does not abolish the current ban. Open Security Policies. You need read permissions to view, you need control permissions to change. Part of the limitations of a particular node is also on its Z Limitations and Prohibits tabs.

Passwords and panel authorization

The minimum length and complexity of the password, the age of the password and registration, the absolute and inactive duration of the session, the maximum number of authorizations and the thresholds of login attempts are configured. The minimum length is chosen in the range of 15-128 characters. By default, a full local session is limited to eight hours and 30 minutes without activity; see the specific installation values in the policy. When the local password expires, the prescribed procedure for changing with the MFA is required. The Axottle user password is not controlled by Telepúrte’s local password policy: check the source of the registration. To sign in for reverse proxy, consider that the application’s IP limit can see the proxy address. The external proxy must have its own client attempt limit; don’t expect an arbitrary X-Forwarded-For to change the address the application trusts.

User Prohibitions and Roles

The rule can restrict panel entry, SSH, managed shell commands, or file actions. Select recipient, node area, action, cause, and if there is a deadline. For role prohibitions, check inheritance. The domain can refer to a node, a project, a group, a label, or all suitable nodes, and the file rule is further limited to the path, and the source and destination are checked for travel.
The shell command text filter is not a reliable isolation of the interactive terminal. Another syntax or program can perform the same action. To limit your capabilities, use system login, Linux rights, sudo and, if necessary, completely ban SSH.

Prohibition of activities and profiles

A typed operation can be disallowed on a specific node or more broadly by specifying the exact unit, packet, or path, if necessary. It is not a regular expression or a name search. Prohibition is rechecked upon preview, confirmation and issuance to the agent, it can limit the launch of the owner, the already issued operation can be completed after the creation of the ban, the removal of the rule allows future launches, but does not restart previously stopped targets. Managed command profiles have separate prohibitions, and file.ensure_content prohibition should not be considered an automatic ban on a shell command that writes the same file.

Restrictions of the node and bastion

The node has valid SSH logins, SFTP root directories, and connection limits, which complement the grant, for example, allowing a operator user won’t help if only a different login is allowed for the node. Terminal limits apply to the bastion, the user and the node. Reducing the number does not automatically terminate all existing terminals, but can prohibit new, while there are too many active sessions.

Policy change arrangements

First, write down the current values and identify the affected users. Apply a narrow rule to a test node or a record, check the expected failure and save the desired access, then expand the area. Leave the owner’s working local login and independent access to the panel server. If you close your authorization with a new policy, the browser will not be able to use the previous session to cancel it.

Verification

Under a normal user, check the permitted and forbidden action. For files, check the specific path and operation; for mass works, check the new preview; match the result with the audit, and make sure the rule doesn’t affect the extra nodes.

Rollback

Remove a specific ban or return the previous settings from the current administrative session. Completed authorizations are not restored: the user will need a new login. Prohibitions do not return the state of files or services that have already been changed. The set of screens and actions depends on the version of the components and the current rights.