Skip to main content
Myrmex implements a Proprietary Communication Protocol designed specifically for high-stakes cybersecurity operations. This protocol ensures that every interaction between the platform and its multi-agent ecosystem is not only fast but rigorously authorized, auditable, and secure.

​
The Security-First Stack

Unlike generic communication models, the Myrmex protocol is built on the specialized Myrmex InterAgent Backbone Protocol. This proprietary stack adds multiple layers of security and validation required for enterprise environments.

​
Core Security Mechanisms

The protocol enforces a “Verify Everything” model through three critical mechanisms:
Every request sent through the protocol is signed using HMAC-SHA256. This ensures that the execution payload hasn’t been tampered with in transit and definitively proves the origin of the command.
The platform employs a dual-authentication strategy:
  • Service-to-Service: Mutual TLS (mTLS) with internal certificates for agent-to-agent talk.
  • User-to-Action: JWT Bearer tokens that carry the user’s identity and granular permissions.
The protocol includes mandatory timestamp and nonce (unique identifier) fields. This prevents “replay attacks” where a captured valid command might be resent by an unauthorized party.

​
Granular Action Control (Callbacks)

A central feature of the Myrmex protocol is its system of Intercepting Callbacks. Before any sensitive action (like killing a process or modifying a firewall rule) is executed, the protocol triggers a validation loop:
1

Pre-Execution Interception

The protocol intercepts the intent. It validates that the requested tool is allowed for the specific agent and user role.
2

Contextual Validation

It checks organizational guardrails and rate limits to prevent “costly” or unsafe operations from running unchecked.
3

Chain of Custody

The protocol records a “Common Metadata” packet, including who initiated the request, why it was delegated, and precisely which parameters were used.

​
📋 Comprehensive Audit Trail

Every transaction handled by the protocol generates a structured event. This provides a complete Chain of Custody for forensic auditing and compliance reporting.
  • Who: Authenticated User & Organization.
  • What: The specific Myrmex InterAgent Backbone Protocol method and parameters.
  • Result: Success/Failure status and the deterministic output.
  • Traceability: A unique correlation_id that links a user’s initial question to every sub-agent action taken.
This protocol ensures that Myrmex moves at the speed of AI while maintaining the rigor and safety of an expert-led security operation.