DEV Community

OnaEiuspkz
OnaEiuspkz

Posted on

Malcolm Deployments Need an Authentication and Data-Retention Review

Malcolm Deployments Need an Authentication and Data-Retention Review

Malcolm is a network traffic analysis suite that processes packet captures and Zeek logs and presents enriched session data through OpenSearch Dashboards and Arkime. A browser page is only the visible edge. The deployment stores network metadata and may hold packet contents, credentials observed in traffic, and enough context to reconstruct an incident.

An existing AutoPR count-only observation recorded 366 matches for title="Malcolm" && service="http" on October 22, 2026. The title match is a candidate inventory and may include pages that are not Malcolm instances. No live probe was performed for this article, and the count does not establish authentication state.

Authentication is a required design choice

Malcolm's documentation says the interface requires authentication and can use TLS-protected basic authentication, LDAP, embedded Keycloak, or a remote Keycloak instance. It also documents no_authentication as an explicit mode. That mode is not a safe default. If it appears in production, the operational reason and compensating network boundary need to be recorded.

Basic authentication is not equivalent to a complete identity program. It depends on the TLS configuration, account management, password policy, and the absence of an unprotected path. LDAP and Keycloak introduce their own trust decisions: directory group mappings, service accounts, certificate validation, issuer and audience checks, and recovery behavior.

Interpreting the count

The stored query was:

title="Malcolm" && service="http"

The title Malcolm is not unique to this product. Some matches may be unrelated websites, and some Malcolm installations may present a different title or no HTTP title. The 366 result is useful as a bounded discovery lead, not as a claimed number of exposed network-security stacks.

The deterministic search link is:

https://www.zoomeye.ai/searchResult?q=dGl0bGU9Ik1hbGNvbG0iICYmIHNlcnZpY2U9Imh0dHAi

What to review

Confirm the public address and TLS certificate, then determine whether the interface is meant to be internet-facing. If a VPN or identity-aware proxy is required, test the direct origin path as well. A protected DNS name can hide an unprotected IP address.

Review the authentication mode and the account source. Confirm that an LDAP service account has limited read scope and that group membership maps to an approved role. For Keycloak, validate the issuer, client audience, TLS chain, token lifetime, and the account used for API integration. Check that logout and account removal take effect.

Next, examine what the UI can query. A data-retention policy should state which packet captures, logs, and enrichment records are stored, for how long, and who can download or export them. Restrict Arkime views and OpenSearch Dashboards by role where the deployment supports it. Log data access as well as login events.

Operational limits

The hardware and storage footprint can encourage a team to keep more traffic than it needs. More retained traffic increases the value of an account compromise. The review should include retention, backup access, key management, and the process for removing a tenant or investigation dataset.

References

Top comments (0)