Comet ML at 70 title matches: service-account reach is the inventory question
Comet ML is used to track experiments, models, and related machine-learning activity. A self-hosted or dedicated Comet deployment can hold source snippets, metrics, artifacts, model identifiers, and the API keys that automation uses to write to the service. The product name in an HTML title is only a starting point for an exposure review.
On November 18, 2026, ZoomEye returned 70 matches for title="Comet ML" and zero for app="Comet ML" with sub_type=all, page 1, and page size 1. The title count is not a count of self-hosted Comet installations. It can include documentation, hosted product pages, and unrelated pages that contain the phrase. The zero application result means the exact application query did not classify a matching asset.
Comet's official documentation describes personal API keys, organization and workspace roles, service accounts, and JWT authentication. A service account is intended for automated work such as webhooks, production monitoring, or data retrieval. The documentation also states that service accounts inherit the permissions of an Organization Admin and can have full read and write access across every workspace in the organization.
Why that inheritance matters
An API key is often treated as a technical convenience. In Comet's model, a service-account key can represent organization-wide authority. If the key is copied into a CI job, notebook, monitoring system, or shared environment, the attacker who obtains it may not be limited to one experiment. They can potentially reach every workspace that the organization account can access.
The first control is separation. Use a service account only where a human login is impractical. Give it a name that records the owner and purpose. Store the key in a secrets manager and restrict which workloads can retrieve it. Do not put the same key in interactive notebooks, scheduled jobs, and production monitoring. A key that appears in three places has three failure paths.
The second control is review. Inventory service accounts, their creation dates, last use, and the number of workspaces they can reach. Check whether the organization still needs each account. Rotate or disable accounts that were created for experiments that ended. A service account with organization-admin inheritance should have a shorter lifetime and a stronger approval process than a personal read-only key.
Comet's JWT feature is a separate authentication path. The documentation says JWT lets users sign requests with tokens issued by an identity provider while Comet continues to authorize calls with existing API keys. It supports a JWKS URI and key rotation. This can improve short-lived credential handling, but it does not remove the need to scope the account that the token maps to. A short-lived token with organization-wide permissions is still organization-wide for its lifetime.
From title matches to a useful inventory
Start with owned domains, cloud load balancers, and Kubernetes ingress records. Confirm the response is a Comet application and identify whether it is cloud, single-tenant, or a custom deployment. Check the login flow, authentication mode, and organization settings. Determine whether public signup is enabled and whether an unauthenticated user can list workspaces or view experiment metadata.
Then test API authorization. A valid low-privilege user should not be able to read another workspace's artifacts or create a service account. A service account should be tested against the specific API operations it needs. The fact that the UI hides an admin button is not evidence that the endpoint enforces the same rule.
Finally, protect the data in the experiments. API keys, cloud credentials, and model-provider tokens are sometimes pasted into notebook cells or logged as parameters. Redact those values before they reach experiment metadata. Rotate any credential that was stored in a workspace accessible to a broad service account.
Seventy title matches do not prove 70 exposed Comet installations. They do provide a bounded reason to check whether any of those pages belong to the organization and whether a service-account key is doing more work than its owner intends.
Query evidence
title="Comet ML"
sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:42:24+08:00, count=70
Top comments (0)