Security Architecture & Data Safeguards

AetherKube never requires public ingress, open load balancers, or inbound firewall pinholes into your private VPC or on-premise Kubernetes clusters.

• In-cluster agent initiates outbound-only mutual-TLS WebSocket connection to your control plane hub.
• Zero listening ports exposed on worker nodes or control planes.
• Compatible with air-gapped datacenters, AWS private subnets, Azure VNet, and GCP Private Service Connect.
• Immediate auto-reconnection and cryptographic session renegotiation on network blips.

Your Kubernetes secrets, customer application payloads, and proprietary workloads remain 100% within your operational boundary.

• Client-side secret sanitization strips sensitive tokens, passwords, and environment variables prior to diagnostics.
• Zero telemetry or prompt data is sent to external AI providers when running in deterministic or local Ollama mode.
• Deterministic Kubernetes diagnostics operate 100% offline with zero internet connectivity required.
• No silent phone-home tracking or unauthorized external metrics collection.

Enterprise license keys are validated locally using HMAC-SHA256 signatures with offline tolerance and graceful degradation.

• HMAC-SHA256 signature verification occurs locally on your machine or server.
• 7-day offline grace period protects operations during transient WAN connectivity loss.
• Safe degradation: when a license expires, the system safely operates in Free tier with zero cluster deletion and zero data loss.
• Ctrl+C cancellation traps prevent unverified background application execution.

Self-healing policies enforce strict limits, automated dry-runs, and manual review checkpoints to prevent cascading restart storms.

• Mandatory dry-run manifest evaluation precedes every cluster patch.
• Manual approval workflow required out-of-the-box on Free edition.
• Automated cooldown gates cap restart bursts (e.g. max 2 patch attempts per pod lifecycle).
• Point-in-time SQLite and etcd snapshot backups taken automatically prior to state transitions.

Strict separation of privileges prevents unauthorized kubectl exec, manifest alterations, or cross-tenant cluster leakage.

• Granular role-based access control (Admin, Operator, SRE, Viewer).
• Read-only Viewer role safely inspects telemetry and diagnostic insights without cluster write access.
• Namespace-level tenant isolation restricting visibility and resource quotas across engineering squads.
• PBKDF2 password hashing and signed JWT session token expiration.

Every automated remediation, user action, and diagnostic query is recorded in an immutable, signed audit log.

• Chronological audit records capturing actor, timestamp, target cluster, and patch diff.
• Local disk persistence in structured JSON for compliance auditing.
• Stream audit logs directly to external SIEM systems (Datadog, Splunk, Elastic).
• Tamper-evident logs designed for SOC 2 Type II audit readiness.