Rill's 115 title matches are discovery leads, not public-dashboard confirmations
Rill deployments can serve dashboards, custom APIs, and developer interfaces. A title match can find a product page, but it does not tell an analyst whether a data view is public or whether the runtime holds warehouse credentials. On 2026-10-28 at 22:48 UTC, a bounded ZoomEye SDK probe used the global all scope, page 1, and page size 1. The query app="Rill" returned 0. The query title="Rill" returned 115.
The application query found no exact fingerprint in this probe. The title result is broader and can include unrelated pages where the word appears. Both are discovery observations. Neither is evidence that a dashboard can be read anonymously, and neither shows the connector behind the page.
An approved review should first identify the service type. Confirm whether the response is a Rill Cloud project, a local Rill Developer view, or another page. Then ask for the project owner. Rill Cloud access management distinguishes users, project access, public dashboard URLs, and service tokens. A public dashboard can be intentional; a public development environment with connector credentials is a different decision.
The connector is the next boundary. Rill documentation recommends environment-variable references and warns that credentials from a local .env file can be pushed to a Cloud project. A discovered project should be compared with its credential inventory: which connectors are present, whether they use project or user authorization, which source tables they can read, and when the credentials were last rotated.
Do not test random public pages with data queries. A controlled owner review can check the page from an approved browser, inspect the project access setting, and confirm whether the visible metrics match the intended public classification. If access is private, test unauthenticated access only where the owner has approved that validation.
Keep the query pair together. The absence of an application match and the presence of title matches show how product discovery changes when the title is generic. Re-run both on the same scope and record the time. A count of 115 is modest, which makes ownership follow-up practical even though it does not establish security status.
ZoomEye helps expose projects that are not in the asset register and gives the team a bounded place to start. The security decision remains tied to Rill access settings, connector authority, and the content of the dashboard.
Top comments (0)