Malcolm
cisagov.github.io
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Malcolm is
Malcolm is a network traffic analysis suite for security monitoring. It accepts PCAP files, Zeek logs, and Suricata alerts through a browser interface, as well as live captures forwarded by lightweight sensors. OpenSearch Dashboards provides visualizations, while Arkime helps find and identify network sessions. Malcolm adds context to session data through GeoIP, hardware manufacturer lookups, asset inventory mappings, and JA4 fingerprinting. Documented components include Zeek, Suricata, Arkime, OpenSearch, NetBox, MISP, TAXII, and Google and Mandiant threat intelligence sources. Analysis covers protocols such as DNS, HTTP, Modbus, and BACnet. Deployment uses Docker or Podman containers, with Kubernetes instructions for on-premises or AWS use. A dedicated server requires at least 8 CPU cores and 24 GB of RAM; 16 or more cores and at least 32 GB are recommended for an optimal experience. The interface requires authentication, with local TLS-encrypted basic authentication, LDAP, and Keycloak options. Malcolm is free under the Apache License 2.0.
Who it suits
Malcolm suits security teams and network operators who need to analyze recorded traffic or live captures. Its dedicated-server requirements make it relevant to organizations able to provide substantial compute resources.
Good to know, and what to watch
- Accepts PCAP files, Zeek logs, and Suricata alerts
- Supports live capture through lightweight sensors
- Enriches sessions with GeoIP and JA4 fingerprints
- Offers LDAP and Keycloak authentication options
- Free under the Apache License 2.0
- Dedicated server needs at least 8 CPU cores
- Dedicated server needs at least 24 GB of RAM
- Recommended configuration is 16 or more cores and 32 GB or more RAM
Plans
Every plan and priceMalcolm
Free plan
Getting started
- Open the Malcolm website
- Prepare a host running a recent Linux or macOS release, or Windows 10 or later
- Provide a dedicated server with at least 8 CPU cores and 24 GB of RAM
- Deploy Malcolm with Docker or Podman, or follow its Kubernetes deployment guidance
- Forward live captures from lightweight sensors or load PCAP, PCAPNG, Zeek, or Suricata data
- Configure authentication and access controls for the web interface
Limits to check
The free Malcolm plan is self-hosted software under Apache License 2.0. A dedicated server requires at least 8 CPU cores and 24 GB RAM, while 16 or more cores and 32 GB or more are recommended for an optimal experience.
The Club's review
Malcolm is a self-hosted suite for analyzing network traffic in security-monitoring workflows. It is best suited to teams that need to investigate sessions and enrich traffic data, rather than simply capture packets. Its breadth is a strength, but the recommended hardware makes deployment a substantial commitment.
Overview
Malcolm accepts existing PCAP files, Zeek logs, and Suricata alerts through a browser interface, and can also process live capture forwarded by lightweight sensors. That makes it relevant to both retrospective investigations and ongoing monitoring. The combination of session discovery, visualizations, and enrichment connects those tasks in one suite.
It is not a lightweight desktop utility: Malcolm runs in containers and requires at least 8 CPU cores and 24 GB of RAM on a dedicated server. The recommended optimal configuration is 16 or more cores and at least 32 GB of RAM. Teams without capacity to provide and operate that infrastructure should look to a narrower capture tool.
Key features
- Offline and live analysis: Malcolm supports offline trace analysis and accepts PCAP and PCAPNG files; it also supports live capture, including command-line capture and feeds forwarded by lightweight sensors. This range suits teams investigating stored evidence as well as monitoring incoming traffic.
- Session search and visualization: Arkime helps users find and identify network sessions, while OpenSearch Dashboards provides visualizations. Together they support moving between broader traffic views and session-level investigation.
- Data enrichment: GeoIP, hardware manufacturer lookups, asset inventory mappings, and JA4 fingerprinting add context to session data. This can make traffic findings more useful to teams correlating network activity with devices and assets.
- Security and access controls: The interface requires authentication and supports local TLS-encrypted basic authentication, LDAP, and Keycloak. Role-based access control and Keycloak group and realm role restrictions provide ways to limit access; these options matter when multiple users share a deployment.
- Protocol and ecosystem coverage: Zeek and Arkime analyze documented protocols including DNS, HTTP, Modbus, and BACnet. Documented components and integrations include Zeek, Suricata, Arkime, OpenSearch, NetBox, MISP, TAXII, Google, and Mandiant threat intelligence sources, making the suite relevant where those tools and sources are part of an existing workflow.
Pricing
Malcolm is free: the Malcolm plan costs nothing and is self-hosted software under the Apache License 2.0. There is no paid tier to weigh against the free plan, but free licensing does not remove the server and deployment requirements. It fits organizations able to provide the infrastructure and administer a self-hosted monitoring stack.
Platforms
Malcolm runs in containers using Docker or Podman, with documentation for on-premises or AWS Kubernetes deployment. The recommended requirements page says Docker runs on recent Linux and macOS releases and Windows 10 or later. Users interact through a web browser, and a REST API is supported. These deployment options offer flexibility for infrastructure teams, but do not make the underlying compute requirements small.
Who it's for
Malcolm is a strong fit for security teams that need to combine capture analysis, session search, and enrichment, and can dedicate server resources to a containerized deployment. Its protocol coverage and integrations are useful where network monitoring needs context from asset inventories or threat intelligence sources. It is a poor fit for someone seeking a quick, low-resource packet viewer or an environment without staff to manage self-hosted infrastructure.
Pros and cons
- Pro: Supports offline traces and live capture, letting teams investigate saved traffic and monitor forwarded feeds with the same suite.
- Pro: Session search, dashboards, and multiple forms of enrichment provide more investigative context than capture alone.
- Pro: Authentication options and role-based controls support deployments shared across users.
- Con: The minimum dedicated-server requirement of 8 CPU cores and 24 GB RAM is a significant barrier for small deployments.
- Con: Malcolm is self-hosted and container-based, so teams must be prepared to provision and operate its infrastructure.
Alternatives
For a broader set of network packet capture software, compare tools by whether the priority is full monitoring and enrichment or focused capture and inspection.
- Arkime is a free, self-hosted option when session search is the priority and Malcolm's wider suite is unnecessary.
- Termshark is free and supports Linux, macOS, Windows, and Android; choose it when a narrower tool that requires tshark is a better fit than Malcolm's server deployment.
- Wireshark is free on Linux, macOS, and Windows, making it an alternative when packet inspection is the goal rather than Malcolm's enriched monitoring workflow.
- tcpdump is a free, BSD-licensed choice for teams seeking a focused capture tool; capture permissions depend on operating system and configuration.
- Sniffnet is free and open-source for Linux, macOS, and Windows when a standalone traffic-monitoring option is preferred.
- Colasoft Capsa offers a Windows free plan limited to monitoring 10 IP addresses, with a four-hour session timeout and no WiFi connection monitoring; consider it when those limits suit the use case.
- NetworkMiner is a freemium alternative with free, open-source software released under GPLv2; consider it when that approach is a better match than Malcolm's containerized suite.
- PCAPdroid is an Android freemium option when monitoring and capture on Android matter more than Malcolm's server-based workflow.
Verdict
Choose Malcolm if your security team needs live and offline traffic analysis, session search, enrichment, and access controls in a self-hosted suite. Its main advantage is bringing those capabilities together; its main drawback is the server capacity and operational commitment it demands. If you only need packet capture or inspection, a focused alternative is the more proportionate choice.
The verdict
Malcolm combines traffic analysis, session search, and data enrichment for network security monitoring, with container and Kubernetes deployment options. Plan for its stated hardware requirements before deploying it.
Questions people ask
How much does Malcolm cost?
Malcolm is free. Its listed plan is free under the Apache License 2.0 for self-hosted software.
Which platforms can run Malcolm?
Malcolm supports Linux, macOS, Windows, web browsers, and a REST API. Deployment uses Docker or Podman, with Kubernetes guidance for on-premises or AWS environments.
What data can Malcolm analyze?
It accepts PCAP and PCAPNG files, Zeek logs, and Suricata alerts. Live capture can be forwarded by lightweight sensors.
Does Malcolm support live capture and offline analysis?
Yes. It supports live capture, offline trace analysis, display filters, and command-line capture.
How is access secured?
The interface requires authentication and supports local TLS-encrypted basic authentication, LDAP, and Keycloak. Documentation also describes role-based access control.
What the maker publishes
- Access control
- The documentation describes role-based access control and Keycloak group and realm role restrictions for limiting which users can authenticate. source
- Analysis interfaces
- It provides OpenSearch Dashboards for visualizations and Arkime for finding and identifying network sessions. source
- Data enrichment
- Malcolm enriches network session data with GeoIP, hardware manufacturer lookups, asset inventory mappings, and JA4 fingerprinting. source
- Deployment
- Malcolm runs in containers using Docker or Podman, and documentation also describes Kubernetes deployment on premises or in AWS. source
- Host platforms
- The recommended requirements page says Malcolm runs on Docker on recent Linux and macOS releases and Windows 10 or later. source
- Input data
- It accepts PCAP files, Zeek logs, and Suricata alerts through a browser interface or from live capture forwarded by lightweight sensors. source
- Integrations
- Its documented components include Zeek, Suricata, Arkime, OpenSearch, NetBox, MISP, TAXII, Google, and Mandiant threat intelligence sources. source
- License
- The project says it is licensed under the Apache License, version 2.0. source
- Protocol coverage
- Malcolm uses Zeek and Arkime to analyze traffic across documented protocols including DNS, HTTP, Modbus, and BACnet. source
- Purpose
- Malcolm is a network traffic analysis tool suite for network security monitoring. source
- Security
- Malcolm requires authentication for its user interface and supports local TLS-encrypted basic authentication, LDAP, and Keycloak authentication. source
- System requirements
- A dedicated server requires at least 8 CPU cores and 24 GB of RAM; the developers recommend 16 or more cores and 32 GB or more RAM for an optimal experience. source
Checked against the maker's pages on 29 Sept 2026.