Wazuh Counts Are Broad, so Dashboard RBAC and Tenant Scope Need Evidence
Wazuh combines endpoint agents, a server API, an indexer, and a dashboard. A product-level internet count is likely to include more than one of those components. Reviewing exposure requires a narrower question: which reachable endpoints are dashboards or management APIs, and what data and actions do their identities authorize?
What the measurement found
On 2026-11-19, a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="Wazuh" returned 18,191. title="Wazuh" returned 18,016. http.body="Wazuh dashboard" returned 1,317.
The first two values are very close and do not distinguish endpoint, server, indexer, dashboard, or documentation pages. The body query is narrower but still not proof of a dashboard. These counts describe indexed signatures, not confirmed unauthenticated access.
Map the component graph
Start with the public URL and identify whether it reaches the dashboard, the Wazuh server API, or the indexer. The dashboard is the user interface, but it depends on services that may have their own authentication and network paths.
Wazuh documentation describes role-based access control, SSO integrations, role mapping, tenants, and read-only roles. A dashboard login can therefore represent several layers: identity-provider authentication, role mapping, indexer permissions, tenant selection, and server API authorization.
Record each layer and the group or role that controls it. A read-only role should be tested against index management, agent configuration, and response actions, not only against alert viewing.
Review tenants and data scope
Multi-tenancy can separate dashboards and saved objects, but documentation warns that it does not automatically isolate all index data. Review the index patterns, tenant assignments, and roles together. If two teams share a dashboard but should not see each other's alerts, test with representative accounts from both teams.
Check SSO role mapping. An identity provider group name is not sufficient until the product maps it to the intended local role and tenant. Confirm that default or broad roles do not apply when a mapping is absent.
Validate the external path
Use owner confirmation and an approved unauthenticated request to identify a candidate. Do not log in with guessed credentials or exercise response actions. Check whether reverse-proxy rules expose the dashboard while blocking the API and indexer from the same external network.
Review TLS, session policy, authentication token lifetime, and administrator access. Then test an allowed read and a denied administrative action. Save the evidence with version and configuration context.
The broad counts show that Wazuh is common in indexed web content. They do not support a statement that thousands of dashboards are open. The defensible review identifies a dashboard, maps its identity and tenant model, and confirms that sensitive actions are denied to the roles that should not perform them.
References
- Wazuh dashboard, Wazuh documentation. Retrieved 2026-11-18.
- Wazuh RBAC, Wazuh documentation. Retrieved 2026-11-18.
- Enabling multi-tenancy, Wazuh documentation. Retrieved 2026-11-18.
- Wazuh server API configuration, Wazuh documentation. Retrieved 2026-11-18.
- ZoomEye counts:
app="Wazuh"18,191;title="Wazuh"18,016;http.body="Wazuh dashboard"1,317.sub_type=all, page 1, pagesize 1, observed 2026-11-19 UTC+8.