Razuna's small public footprint still carries digital-asset authority
Razuna is a digital asset management system. A deployment can hold brand media, press material, product photography, documents and internal creative work. The public footprint is small, which makes the candidate list easier to review, but the count still does not show who can read or change an asset.
Measurement
A standalone ZoomEye SDK run on 2026-11-15 used sub_type=all, page 1 and pagesize=1:
| Query | Matched assets |
|---|---|
app="Razuna" |
15 |
title="Razuna" |
41 |
http.body="Razuna" |
126 |
The application fingerprints and title matches provide a narrow starting set. The body count is broader and can include product pages, documentation and customer references. None of the values is a count of vulnerable or publicly readable libraries.
API keys inherit a user's reach
Razuna API documentation places an API key in the user dialog and shows the key in request parameters. The key can perform asset and user operations according to the product's API surface. The documentation states that API keys are per user. A key used by a publishing workflow should not belong to a global administrator merely because that account can see every collection.
Review the API key owner, role, workspace, folder and asset access. Confirm whether a key can add or update users, delete assets or change permissions. Rotate a key when the owning account changes role or leaves, and record which external service stores the value.
The API may use query parameters for convenience. That placement creates a logging problem: web servers, proxies and support tools can capture a URL containing the key. Prefer a supported header or body transport when the API and client allow it, and redact the key from every log path.
Automation ownership matters as the integration expands. A key created for one upload job can acquire more permissions when a user changes roles or when a new endpoint is added. Record the key's purpose and expected operations, then test that it cannot perform unrelated account or deletion actions.
Asset permissions need the same map
Razuna documentation describes group and user management, and its current product material describes view-only access at workspace, folder or asset level. A public marketing library can be intentional. An internal brand source, unreleased product image or signed document should have a different permission set.
Test anonymous access, a viewer, an editor and an administrator against one asset. Check direct download, preview, metadata, search and sharing routes. Removing an asset from a gallery does not necessarily remove the underlying file URL.
Reconcile the small list
The 15 application matches should be matched to owned domains, certificates and DAM inventory before any deeper review. For each owned instance, record the version, identity provider, API integrations, storage backend and backup access.
Razuna's small population reduces discovery noise. It does not reduce the authority of an administrator key or the sensitivity of a creative archive. The useful result is a verified permission boundary, not a larger count.
Top comments (0)