Anchore Enterprise is a software-supply-chain security product. Its UI can scan repositories and images, edit policies, manage users and roles, and display vulnerability and policy reports. That combination gives the dashboard both security evidence and administrative authority.
What the measurement found
A count-only ZoomEye SDK query on 2026-11-19 used sub_type=all, page 1, and pagesize 1. app="Anchore Enterprise" returned zero. title="Anchore" returned 122. http.body="Anchore Enterprise" returned 53.
The title value is the broadest of the three. It may include community tools, documentation, marketing pages, or enterprise deployments. The app result is a reminder that an expected fingerprint is not guaranteed to appear.
Review the role model
Anchore Enterprise documentation describes RBAC for controlling user permissions over resources. It also states that the UI shows the permissions granted to members of each role. The first review step is to inventory roles, account scopes, and role members, then compare each role with the actions it actually needs.
A user who can view scan results should not automatically edit policies, manage repositories, or assign roles. Review account-level and system-level authority separately. Check the service accounts used by automation because their tokens may outlive the individual who created them.
Review the proxy and UI configuration
Anchore documentation describes Enterprise UI configuration, RBAC service integration, and proxy-aware settings. When the UI runs behind a reverse proxy, confirm that the proxy forwards the expected scheme and identity context. A proxy mistake can break cookie security or alter the authentication path.
The current release documentation also lists a fixed authorization flaw in the RBAC role-membership API, tracked as CVE-2026-63727. That is a concrete reason to verify the deployed version and to test role assignment rather than assuming that the presence of RBAC means the role boundary is sound.
Test privilege boundaries
Create representative roles: report reader, policy editor, repository manager, and administrator. For each, test an allowed action and a denied action. Include role assignment and account management in the matrix because those paths can change future authority.
Check API access separately from the UI. A hidden button is not an authorization control. Review direct calls to the underlying service and confirm that the role check occurs at the service or policy layer.
Confirm deployment ownership
Use the title and body matches as leads, then confirm the host with the product owner. Determine whether it is a SaaS endpoint, a self-hosted Enterprise UI, a community page, or a documentation mirror. Do not attempt authentication or submit scan jobs during discovery.
The useful evidence is version, exposure boundary, authentication provider, RBAC configuration, role mapping, and tested denials. The counts alone do not show that 122 systems are exposed. They show that Anchore-related pages exist and that the next step is a controlled check of the actual UI and its authority.
References
Enterprise UI Configuration, Anchore Enterprise documentation. Retrieved 2026-11-18.
Role-Based Access Control, Anchore Enterprise documentation. Retrieved 2026-11-18.
Using the Anchore Enterprise UI, Anchore Enterprise documentation. Retrieved 2026-11-18.
Anchore Enterprise 6.0.1 release notes, Anchore Enterprise documentation. Retrieved 2026-11-18.
ZoomEye counts:
app="Anchore Enterprise"0;title="Anchore"122;http.body="Anchore Enterprise"53.sub_type=all, page 1, pagesize 1, observed 2026-11-19 UTC+8.