Rudder is a configuration-management platform with a web interface, a policy server, relays, and managed nodes. Its user-management documentation separates authentication from authorization. Users must be declared before they can access Rudder, and their roles and individual rights determine which pages, actions, and API calls they can use.

That makes the Rudder web application a control plane for node configuration. A user who can change directives or rules may be able to alter services across many machines. A user who can read inventories may see hostnames, addresses, software, and operating-system details. The browser login is the entry point, but the role map is the real boundary.

The documentation notes that external LDAP or OIDC authentication does not automatically grant authorization. A user accepted by the external provider but not declared in Rudder has no rights. This is a useful fail-closed default, but it requires the organization to maintain the role and tenant mapping. A successful SSO login is not proof that the user can manage nodes.

Query plan

Use app="Rudder" and title="Rudder" with sub_type=all, page 1, and page size 1. The title is short and may appear in product documentation or unrelated pages. The application field may identify the server component but should not be assumed to identify every relay. No live counts were collected in this run because the authorized ZoomEye execution path was rejected by the execution platform.

Preserve both observations separately if a later measurement is approved. Do not treat a match as a policy server without checking ownership and response content. A relay or node with a similar product name has a different authority scope.

Review roles and tenants

List built-in roles, custom roles, and individual rights. Map them to the work each operator performs. A read-only auditor does not need write rights for rules or nodes. A deployment automation account should use a scoped API token, not a shared administrator password.

The standard API documentation says API accounts are separate from user accounts and, without the API-authorization plugin, have full administrative privileges. That makes a token equivalent to a powerful password. The plugin documentation describes personal API tokens and custom endpoint ACLs. If the plugin is available, use a narrow token for each integration and verify that the endpoint restriction actually applies.

Review tenants if the installation uses them. Tenant membership can limit which nodes and rules an operator sees, but it does not replace the underlying role checks. Test a user who belongs to one tenant and confirm that a direct API request for a node in another tenant fails.

Test the login path

Review the local rudder-users.xml roles and the external provider mapping. Test a provider-authenticated user who has no Rudder role. Confirm that the account receives no management rights. Review the login-form setting when SSO is enabled, including the emergency local login path.

Check password, session, and API-token handling. Remove departed users and stale API accounts. Record the creation and last-use time of every token. A token that can change a policy or run a directive should be reviewed more often than a read-only compliance token.

Monitor the control plane

Monitor logins, role changes, policy edits, node membership changes, API calls, and failed authorization. A configuration change can be a legitimate deployment or an attempt to execute code across the fleet. Correlate Rudder events with the identity provider and the change-management record.

Put the Rudder console and API behind a management network or identity-aware proxy. Restrict node enrollment and relay communication to the expected network paths. Do not expose the policy server on a public address merely because the login page requires a password.

Respond to a match

Confirm ownership through DNS, certificates, and the organization's platform inventory. If the host is authorized, review the user and API-account list before disabling anything. If it is unknown, preserve evidence without logging in. A Rudder title or application match is a prompt to inspect fleet authority, not proof that a server is misconfigured.

References