Platform & Network Security
Planbok's security extends beyond the cryptographic protocol into every layer of our infrastructure. We employ enterprise-grade network protections and hardware-backed secret management to ensure a resilient and secure operating environment.
Infrastructure Isolation
The core of our "No Single Point of Failure" promise is the physical and logical separation of our MPC nodes.
1. Namespace Isolation
Node 1 and Node 2 are deployed in strictly isolated Kubernetes namespaces. Communication is restricted at the network level using NetworkPolicies, ensuring that only authorized services can reach the MPC engines.
2. Multi-Region distribution
In production environments, Node 1 and Node 2 are distributed across separate cloud regions. This protects against regional outages and ensures that a compromise of a specific infrastructure provider's region does not expose both key shares.
Hardware-Backed Security (HSM)
At the persistence layer, all sensitive material—including key shares, API secrets, and encryption keys—is managed by HashiCorp Vault.
- Hardware Security Modules (HSM): Vault is configured to use HSMs for root-of-trust, providing hardware-backed encryption that meets FIPS 140-2 Level 3 standards.
- Dynamic Secrets: We utilize dynamic, short-lived credentials for database and infrastructure access, minimizing the risk of long-term credential leakage.
- Sealing & Unsealing: Our Vault cluster requires a quorum of high-privilege administrators to unseal, ensuring that no single person can gain access to the system's root secrets.
Network Protection
1. DDoS Mitigation & WAF
Planbok utilizes advanced WAF (Web Application Firewall) rules and DDoS protection to mitigate automated attacks:
- Rate limiting: Enforced at the edge to prevent brute-force and resource exhaustion.
- IP Reputation: Blocking of known malicious IPs and botnets.
- Geo-blocking: Optional restriction of API access based on geographic location.
2. API Security
- Mutual TLS (mTLS): All internal traffic between microservices is encrypted and authenticated using mTLS.
- API Key Scoping: API keys are locked to specific IP addresses and domains, preventing their use if stolen.
- Idempotency: Every critical request (like transactions) is protected by mandatory idempotency keys to prevent duplicate processing during network retries.
Continuous Monitoring
Security is a continuous process. Our platform is monitored 24/7 by:
- Intrusion Detection Systems (IDS): Real-time alerting for suspicious network patterns.
- Automated Vulnerability Scanning: Daily scans of our containers and dependencies for known CVEs.
- Anomaly Detection: Machine learning models that identify unusual transaction patterns or access spikes.