Skip to content

Panovista Proxy Core Engine V3.0.1 (Enterprise Edition)

Latest

Choose a tag to compare

@ianayliffe ianayliffe released this 21 Jul 10:13
· 5 commits to main since this release

This release officially introduces the Panovista Product-Led Growth (PLG) Evaluation Tier and hardens the Offline Cryptographic Sovereign Tier. V3.0.1 patches critical memory and cache bugs while strictly enforcing Layer 7 Zero-Trust boundaries for enterprise AI workflows.

🔒 Security Enhancements & Compliance

  • Format-Preserving Tokenization (FPT): Volatile memory swapping of sensitive PII to maintain strict GDPR and Article 12 privacy boundaries.
  • Cryptographic Replay Attack Mitigation: Enforces a rigid 30-second SHA-256 cache window for inbound JSON-RPC IDs to drop duplicated/replayed payloads.
  • Offline Enterprise Licensing: Fully activated PANOVISTA_LICENSE_TOKEN pipeline relying on Ed25519 cryptographic identity verification.
  • Algorithmic Complexity Traps: Hardcoded fail-closed JSON depth limit (20 layers) to prevent memory exhaustion (DoS).
  • Egress Volume Choking: Hard limit of 5MB per downstream payload to prevent catastrophic intellectual property (IP) extraction.

🛠 Bug Fixes & Stability

  • Replay Cache Bug: Resolved false-positive cache hits preventing dynamic UUID generation from correctly passing through the inspection engine.
  • Memory Leak & Race Conditions: Cleaned up goroutine management and memory allocation within the recursive de-obfuscation pipeline.
  • Documentation Drift: Completely synchronized and sanitized the DEVOPS_COMPLIANCE_GUIDE.md to reflect accurate V3.0 architectural parameters.

🚀 Deployment Instructions

The enterprise Docker image is fully public and verified on the GitHub Container Registry (GHCR).

Pull the latest engine via:

docker pull ghcr.io/panovista/agent-firewall:v3.0.1
# or pull the latest tag
docker pull ghcr.io/panovista/agent-firewall:latest

For complete implementation parameters, mandatory environment variables, and RBAC compliance configurations, please review the DEVOPS_COMPLIANCE_GUIDE.md located in the root of the repository.