Nussknacker at 25 title matches: the Designer is a policy authoring surface
Nussknacker is a stream-processing and decision-automation platform. Its Designer application lets users build scenarios, configure integrations, and publish logic that runs against data streams. A public Designer page is a place where a user can change the behavior of a production pipeline.
ZoomEye returned 25 matches for title="Nussknacker" and zero for app="Nussknacker" on November 18, 2026, with sub_type=all, page 1, and page size 1. The title count is an index observation. It may include documentation, a demo, or pages with the product name in metadata. The zero application count does not show that no Nussknacker instances are online.
The official Nussknacker documentation describes the Designer as the web application for editing and deploying scenarios. Its security configuration supports BasicAuth, OAuth2, and OpenID Connect. It also documents API tokens for non-human clients, including command-line tools, scripts, CI jobs, and integrations. The token system has configurable lifetime and authorization data staleness, which means a valid token can retain access after the human user's role changes unless the deployment handles that freshness.
Separate authoring from deployment
A person who can view a scenario does not necessarily need to publish it. A person who can edit a test environment should not automatically be able to deploy to production. The Designer should map identity roles to these actions and log the change. If all authenticated users share one role, the login page provides authentication but not a meaningful authorization boundary.
API tokens deserve their own inventory. A token used by CI may need to deploy a scenario, while a token used by monitoring may need only read access. If the platform does not support a narrow role for a token, use a dedicated service identity and restrict its network origin. Set a lifetime that matches the automation, and revoke the token when the pipeline is removed.
The stream-processing configuration also contains sources, sinks, and credentials for Kafka, databases, and external services. A user who can edit a scenario may be able to select a connector that the platform can reach, even if the user cannot reach it directly. Review the platform's network egress and the credentials available to each scenario. A deployment in a developer environment should not share production Kafka or database credentials merely because the Designer is behind a VPN.
What to verify on an exposed page
Check whether the Designer is reachable without a login, whether the login accepts a shared account, and whether the health or metrics endpoints expose version and configuration details. Confirm that API tokens are required for programmatic scenario changes and that the token cannot be used to manage users or security settings. Test an expired token and a token for a removed user. Review the audit log for new scenarios, changes to connectors, and deployments during the exposure window.
The public count is small, which makes a manual review practical. Start with hosts that contain the product name, verify ownership, and compare the observed hostname with the application inventory. Do not use the count as a list of targets. For each owned deployment, record the authentication provider, role mapping, API-token owners, network path, and production connectivity.
Nussknacker can be a legitimate public-facing application when it is designed that way. The relevant boundary is whether an anonymous or low-privilege visitor can change a scenario and whether the scenario can reach data or services outside its intended scope. Twenty-five title matches are a prompt to check that boundary, not a finding that those systems are exposed.
Query evidence
title="Nussknacker" sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:43:30+08:00, count=25 