Evidence · DiggingBeagle record
Connection Escrow: eBPF holds agent egress until policy verifier approval
The Connection Escrow paper presents a Linux eBPF kernel hold and signed, socket-specific release rule for AI-agent network egress. Authors report 36 adversarial checks, 600 connections across six Kubernetes pods and latency measurements; policy-verdict correctness is outside the benchmark proof.
- Source role
- primary disclosure
Evidence record
The Connection Escrow paper presents a Linux eBPF kernel hold and signed, socket-specific release rule for AI-agent network egress. Authors report 36 adversarial checks, 600 connections across six Kubernetes pods and latency measurements; policy-verdict correctness is outside the benchmark proof.
Claim-level citations (3)
- supportsConnection Escrow tests signed agent network approval at the kernel socket boundary: The paper reports a limited adversarial network test suite and sub-10-ms median socket-hold observations, not universal isolation certification.
Evaluation section: adversarial cases and latency
- supportsConnection Escrow tests signed agent network approval at the kernel socket boundary: The authors describe binding outbound connection approval to the process context, destination and actual socket before packet transmission in a Linux prototype.
Mechanism and kernel hook design
- supportsConnection Escrow tests signed agent network approval at the kernel socket boundary: The authors report a 36-check adversarial test suite and 600 socket-gated connections across six pods with a measured median hold of 4.3 ms; these measurements do not validate the correctness of every policy verdict.
Abstract, Evaluation: adversarial suite, Kubernetes cluster and released-connection latency