Skip to content

Security: madgagarin/RXON

Security

SECURITY.md

SECURITY.md

EN | ES | RU

Reporting a Vulnerability

Please report any vulnerabilities in the RXON protocol library to [madgagarin@gmail.com].

Core Principles

RXON is designed to be the secure "nerve system" of the Hierarchical Logic Network (HLN). It enforces:

🛡️ Zero Trust Identity Chain

Every event emitted from a subordinate node includes an origin_worker_id and a bubbling_chain. This prevents spoofing and allows the Orchestrator to audit the entire path of a signal through the holarchy.

📝 Formal Interface Contracts

All communication (Registration, Heartbeats, Skills) is strictly validated against JSON Schemas. This prevents injection attacks and ensures that malformed data is rejected before it reaches the execution engine.

🧬 Reverse Connection (Axon Flow)

Initiative always comes from the subordinate node (Worker/Shell). This eliminates the need for open incoming ports on workers, making them invisible to external network scans and direct attacks.

⏳ Task Ownership & Deadlines

Results are only accepted from the worker currently assigned to the task. Built-in deadline fields prevent the processing of stale tasks and mitigate certain types of replay or delay attacks.

📊 Resource-Aware Telemetry

Granular resource reporting in Heartbeats allows Orchestrators to detect and mitigate resource exhaustion (DoS) before it causes a system-wide failure.

There aren’t any published security advisories