Tracecat is an open-source security automation platform for workflows, case handling, and integrations. A reachable control plane can contain connector credentials, organization roles, workflow definitions, and incident data. That makes a small set of title matches useful for ownership checks even when the visible count looks modest.

Observation

At 07:50 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. The application query app="Tracecat" returned 0 matches. The title query title="Tracecat" returned 32 matches.

The title result is the usable lead. It can include documentation, demos, official project pages, or an instance whose visible title contains the product name. It does not establish that all 32 assets are Tracecat servers, that they belong to the same organization, or that they are reachable beyond a login page.

The authority behind a workflow

Tracecat's public security description mentions role-based access control, attribute-based access control, OAuth2 scopes, and organization or workspace context. The project also describes a credential broker that resolves referenced secrets at execution time. These are separate data planes even though the user sees one automation interface.

An inventory should begin with the people and service accounts that can define or run workflows. Then map which integrations those workflows can call and which secret references they resolve. A role that can edit a workflow may indirectly change the permissions of every scheduled run that uses it.

The official security guidance also recommends avoiding public internet exposure where possible. If remote access is required, place the service behind a controlled identity and network boundary. Review the proxy, VPN, SSO, and direct listener paths rather than assuming the login page is the only entrance.

Questions for each candidate

  • Which organization and environment does the host belong to?

  • Which identity provider and superadmin bootstrap path are active?

  • Can a user create service accounts, agents, or API credentials?

  • Which secrets are referenced by workflows, and who can rotate them?

  • Are workflow logs or incident artifacts stored in a separate service?

  • Can an outbound connector be used as a general-purpose egress path?

ZoomEye helps narrow the external review to 32 title leads and reveals changes over time. It cannot answer those ownership or authorization questions. The next step is a human inventory with a named owner for the host, the secret store, and each connector.

References