Placement
Install on Linux hosts you intend to protect. XDP acts on selected interfaces; it does not cover every route through a network.
Loading HoneyMesh...
Loading HoneyMesh...
For security and infrastructure teams
HoneyMesh adds a host protection and coordinated response layer to existing security controls. Use this guide to decide where it fits, run a controlled pilot, and prepare a purchase review.
Install on Linux hosts you intend to protect. XDP acts on selected interfaces; it does not cover every route through a network.
The tested 2.3.6-rc2 packaged service requires Linux kernel 5.8 or newer for its capability model. Validate distribution and architecture against the exact release you deploy.
The packaged service uses a dedicated honeymesh user and bounded capabilities. Mesh peers need individual certificates and explicit trust configuration.
Local Community operation and Pro mesh sharing differ. Pro sharing requires a valid license and an operator opt-in.
Choose an allowlist, observe-first policy, ban review owner, rollback procedure, and support contact before enforcing on production interfaces.
Run this on systems you own or are authorized to test. Keep existing firewall, identity, and monitoring controls in place.
Choose representative Linux hosts and interfaces. Record the services, normal traffic, kernel, architecture, and existing network controls.
Install, configure traps and trust, and review events without enforcing bans. Confirm logs, certificates, and operator access.
Test configured detection with authorized traffic, then issue a manual ban. Confirm the protected interface, peer acceptance, and that an unbanned control source still reaches the same services.
Record detection accuracy, false positives, local and remote enforcement time, control-source reachability, service health, CPU/load, peer reconnect behavior, and time to release a mistaken ban.
The federation PoC covers the operator-ban path. An automatic-detection pilot must separately measure detection and false-positive behavior before making a production claim.
Three-node AMD64 manual-ban test, limits, and downloadable PDFs
Interactive browser simulation for operator workflow
Published package versions, checksums, manuals, and licensing files
Architecture, trust controls, sharing boundaries, and operating model
Marketplace purchase status and the current buyer path
Two response paths, prerequisites, procedure, and scorecard
Architecture boundaries, review questions, and fulfillment path
A company review should cover software version and support lifecycle, agent privileges, release integrity, vulnerability handling, data flows and retention, certificate and license management, incident reporting, EULA, privacy terms, support response, and cancellation. Request current documents and terms from Network Decode before relying on them as contractual commitments.
Paid purchasing is planned through AWS Marketplace. The approved listing, when live, will control public price and contract terms. Buyer registration and Pro access must be verified after purchase.
Ask for the security and procurement pack