Directus wraps a SQL database with an API and a data studio. That makes its exposure review different from a static web page. The login screen is only one route. The project may also serve REST and GraphQL endpoints, files, webhooks, flows, and a public policy for unauthenticated requests.

A count-only ZoomEye query on 2026-11-21 measured app="Directus" at 12,498 index matches. title="Directus" returned 1,248. Both used sub_type=all, page 1, and page size 1. The application count is a broad product lead. It does not tell us which collections are public, which policies are assigned, or whether a particular match belongs to the organization. Those require owner-side verification.

Directus documentation describes access control through users, roles, policies, and collection-and-action permissions. Policies are additive. Public-role permissions apply to unauthenticated requests, including requests from bots and scripts. If collection-level read is enabled on the public policy, all items in that collection become reachable through the API unless item filters or other policy rules narrow the result. That is a much better review target than guessing from the Studio's appearance.

Static access tokens are also tied to a user and inherit that user's permissions. The documentation notes that the token is stored in the directus_users collection and is visible in the Data Studio or through the Users API to an administrator. A token is therefore a durable credential with the same effective policy as its user. Do not treat it as a separate service role. Scope the backing user tightly, rotate the token, and use API-only users where possible.

A public Directus surface should be checked in a specific order. First, identify the project and ownership through normal administrative records. Second, list the public policy's collections, actions, fields, and item rules. Third, test only the public routes that the owner intends to expose. Fourth, inspect file and asset permissions separately from collection permissions. Fifth, review flows and webhooks for actions that a public request can trigger.

Network controls still matter. The Studio is a management interface. Put it behind an identity-aware proxy or a private network. If a public front end needs Directus APIs, serve those APIs through a route with explicit CORS and rate limits. Do not publish the Studio merely because the API is public. Keep database ports private, and ensure that the API server cannot read arbitrary local files or execute arbitrary external URLs through a misconfigured flow.

For an inventory owner, the ZoomEye count is useful for coverage. Compare it with the organization's known hostnames and application records. If a match resolves to an unexpected deployment, ask the owner to produce the public policy and effective permissions. Do not submit test writes or enumerate collections that are not yours.

Directus is valuable because one data model supports many interfaces. That flexibility also means the public policy, API, and Studio need separate reviews. The policy is the boundary, not the visual login page.

Exact query: app="Directus"

Open the normalized ZoomEye search

References