RMB uses per-device cryptographic identity, outbound device connectivity, replay resistance, revocation, logical-call idempotency, policy classification, bounded output/timeouts and secret/environment filtering.
Public launch requires a formal security and supply-chain gate, trusted platform packaging where required, rollback evidence and no unresolved critical blocker.
Report security issues through the verified production support/security channel without including unrelated customer data.