Proxy Re-Encryption (PRE)

A unidirectional PRE scheme allows the proxy to transform ciphertexts from Alice to Bob but not from Bob to Alice without a separate delegation key. This is the standard for secure data sharing, as it prevents the proxy from reversing the flow of information. In contrast, bidirectional schemes use a single delegation key that enables transformation in both directions, which is computationally efficient but requires a higher degree of mutual trust between the delegator and delegatee.

This property defines the re-encryption chain depth.

• Single-Hop: A ciphertext can be re-encrypted only once. If Alice delegates to Bob, Bob cannot re-delegate that ciphertext to Carol. This provides strict access control and prevents transitive trust.
• Multi-Hop: A ciphertext can be re-encrypted sequentially multiple times (Alice → Bob → Carol). This enables cascading data sharing workflows but requires careful management to prevent unauthorized downstream access.

In a transparent PRE scheme, the delegatee (Bob) uses his standard private key to decrypt a re-encrypted ciphertext, without any awareness that re-encryption occurred. The process is invisible to the end recipient. In a non-transparent scheme, Bob requires a separate, delegation-specific secret key. Transparency simplifies key management and is preferred for seamless user experiences in production systems.

Collusion resistance defines the scheme's resilience when the proxy and delegatee conspire to recover the delegator's secret key.

• Collusion-Safe (Non-Transferable): Even if the proxy and Bob combine their knowledge (re-encryption key and Bob's private key), they cannot compute Alice's full private key. This is a critical security property for untrusted proxy environments.
• Collusion-Insecure: The proxy and delegatee can collude to expose the delegator's private key, limiting use to fully trusted proxies.

This property governs the delegation key generation process.

• Interactive: Alice must engage in a multi-round protocol with Bob (or a trusted third party) to generate the re-encryption key. This requires Bob to be online and cooperative.
• Non-Interactive: Alice can generate the re-encryption key independently using only her private key and Bob's public key. This is essential for asynchronous, scalable systems where delegates may be offline or unknown at key generation time.

A key-optimal PRE scheme ensures that the delegatee's ciphertext size and decryption cost remain constant regardless of how many times the ciphertext has been re-encrypted. Without this property, a multi-hop ciphertext would grow linearly in size and computational complexity with each hop, making it impractical for deep delegation chains. Key optimality is a standard requirement for efficient, production-grade multi-hop schemes.

PRE enables dynamic patient consent management by allowing a semi-trusted proxy to re-encrypt data for new recipients without ever accessing plaintext. When a patient consents to share their genomic data with a research institution, the hospital's proxy transforms ciphertext encrypted under the hospital's key into ciphertext decryptable only by the researcher's key.

• Granular revocation: Revoking access requires simply ceasing re-encryption operations
• Auditable trail: Every re-encryption event can be logged immutably
• Patient sovereignty: The data owner retains ultimate control over who can decrypt their protected health information (PHI)

In federated learning scenarios, PRE secures the transmission of encrypted model gradients between hospitals and a central aggregation server. Each hospital encrypts its local model updates under the aggregator's public key, and a proxy can re-encrypt aggregated results back to individual participants without the proxy learning the model parameters.

• Prevents gradient leakage: Even if the proxy is compromised, model updates remain ciphertext
• Non-collusion guarantees: The proxy and recipients cannot collude to decrypt data intended for other parties
• Scalable architecture: Supports hundreds of participating clinical sites with minimal key management overhead

Hospitals can store encrypted electronic health records (EHRs) in cloud environments while delegating re-encryption capabilities to a cloud-hosted proxy. When a specialist requires access, the proxy transforms the hospital-encrypted records into ciphertext the specialist's device can decrypt, all without the cloud provider seeing patient data.

• Zero-knowledge cloud: The storage provider never possesses plaintext or decryption keys
• Delegation without decryption: Eliminates the need for the data owner to be online to grant access
• Emergency access protocols: Pre-authorized break-glass re-encryption policies for critical care scenarios

Pharmaceutical companies running multi-site clinical trials use PRE to securely aggregate patient outcomes from disparate hospital systems. Each site encrypts trial data under the sponsor's key, and a neutral third-party proxy re-encrypts the data for statistical analysis without ever viewing individual patient responses.

• Blinded analysis: Statisticians receive re-encrypted data without site-level identification
• Regulatory compliance: Satisfies GDPR and HIPAA requirements for cross-border data transfers
• Immutable provenance: Cryptographic proofs ensure data integrity from collection to analysis

Wearable medical devices and remote patient monitoring systems generate continuous encrypted telemetry. PRE allows a healthcare proxy service to re-encrypt this streaming data for multiple consumers—primary care physicians, specialists, and AI diagnostic systems—each with distinct decryption keys, without buffering plaintext at the edge.

• Bandwidth-efficient: Single encrypted stream serves multiple authorized recipients
• Device-agnostic: Works with constrained IoT hardware that cannot manage complex key distribution
• Real-time access control: Instantly grant or revoke specialist access to live patient vitals

Combining PRE with distributed ledger technology creates tamper-proof audit trails for healthcare data access. Each re-encryption operation is recorded on-chain, providing immutable evidence of who accessed what data and when, while PRE ensures the underlying patient data remains encrypted throughout the logging process.

• Cryptographic non-repudiation: Access events are mathematically provable
• Smart contract integration: Automate re-encryption policies based on consent tokens
• Regulatory readiness: Provides auditable proof for HIPAA accounting of disclosures requirements