Skip to main content
Deploying LIOP across production environments requires establishing zero-trust network segmentation. Unlike centralized API gateways where all traffic converges into a single cluster, LIOP structures nodes across three security tiers:
  1. Tier 1 (Sovereign Enclaves): Isolated database and vault hosts executing in-situ WASI logic (Vault, Bank). Never expose public WAN ports.
  2. Tier 2 (Consortium & Edge Nodes): Shared validation and regional routing services (Oracle, Edge IoT, Nexus OIDC).
  3. Tier 3 (Perimeter Gateways & Relays): Public or DMZ-facing reverse proxies (Border LIO Gateway, Circuit Relay v2).
Sovereign Enclaves & TEE Attestation FlowSovereign Enclaves & TEE Attestation Flow

Sovereign Enclaves & TEE Attestation Flow


1

Configure Network Isolation via Swarm Keys (libp2p/pnet)

LIOP nodes communicate over a private overlay network protected by a 256-bit Pre-Shared Key (PSK). Any rogue node without the PSK is rejected at the transport layer before any Kademlia DHT routing packets are parsed.Generate a standard 32-byte cryptographic key formatted for libp2p/pnet:
Mount this file into your node container or point LIOP_SWARM_KEY_PATH to it:
2

Deploy Docker Compose Production Mesh Orchestration

Below is the production deployment manifest (docker-compose.production-audit.yml topology):
3

Configure Mutual TLS (mTLS) with CertManager

For enterprise compliance (PCI-DSS Req 11.3 and HIPAA §164.312(e)(1)), inter-node gRPC channels enforce mutual TLS authentication:

4. Corporate Firewall & Port Configuration Matrix

Configure edge firewalls and container security groups to permit only designated protocol traffic: