Security Model: Eavesdropper on the Broadcast
Two Security Questions for Coded Caching
Chapter 12 addressed demand privacy: users should not learn each other's demands. This chapter addresses a complementary question: delivery secrecy. An external eavesdropper overhears the broadcast transmission . Can we design a coded-caching scheme such that learns nothing about the file library?
These are two different threat models:
- Demand privacy (Ch 12): Internal users are the adversary β each user must not learn other demands.
- Delivery secrecy (Ch 17): External eavesdropper is the adversary β must not learn any file content from the broadcast.
Both are relevant in practice: privacy for user protection in shared-link services; secrecy for untrusted networks (wireless broadcast where the medium is open).
Definition: Secure Delivery Model
Secure Delivery Model
The secure coded-caching model (Sengupta-Tandon-Clancy 2015) consists of:
- A server with library .
- Users with caches of size bits each.
- An external eavesdropper observing the full broadcast .
Security requirement: for any demand vector , (perfect information-theoretic secrecy of the library).
Correctness: each legitimate user can decode from its cache and the broadcast .
The eavesdropper sees only , not the caches. The caches are pre-distributed privately during off-peak (e.g., via physical storage, secure link, or asymmetric keying). The broadcast phase is the only attack surface.
Theorem: Secrecy Requires
For perfect-secrecy coded caching with users, files, and cache size per user, a necessary condition is . No secure scheme exists with .
The eavesdropper observes . By the cut-set bound, to decode each file a user needs the sum file (bits of info). For secrecy, must be independent of , so carries "zero information" β all information must come from the cache. Hence .
Cut-set setup
User decodes from . By Fano: for some small .
Secrecy condition
Perfect secrecy: .
Combining
.
Conclusion
, so as . The cache must store at least one full file's worth of random key material.
Why : Intuition
Think of the cache as a one-time pad store. To decode a requested file securely, the user needs enough key material to "unmask" the transmission. A one-time pad requires key length = message length = 1 file. Hence .
Coded caching's multicasting gain still applies above the floor: extra memory provides the MAN rate reduction. So effectively, replaces in the rate formula.
Secrecy-Rate-Memory Tradeoff
Secure rate (STC 2015) shifts the MAN curve by 1 file in memory (). At : secure rate = uncoded MAN. Below : no secure scheme. Plot both curves for comparison.
Parameters
Example: Wireless Eavesdropper Scenario
A CDN operator streams video over a wireless broadcast link to users. An eavesdropper in range also receives the signal. videos, per user. Quantify security margin.
Feasibility check
β secure scheme exists.
Effective memory
. Effective ratio .
Secure rate
files/channel-use.
Non-secure MAN baseline
.
Penalty
Secure rate () is worse than non-secure MAN (): secure delivery costs files per use. The 1-file cache is spent on key material.
Leakage
Eavesdropper: by construction. Perfect secrecy achieved at cost of increased rate.
Common Mistake: Don't Conflate Privacy and Secrecy
Mistake:
Assuming demand-privacy schemes (Wan-Caire, Ch 12) also provide secrecy against external eavesdroppers.
Correction:
- Demand privacy masks which file each user wants from other users. The broadcast itself may still leak file content to an outsider.
- Delivery secrecy prevents from learning file content. Does not address which file a particular user requested (that's privacy).
In many scenarios you want both. Joint schemes exist (STC 2015 + Wan-Caire masking), but each primitive addresses only one threat.
Key Takeaway
Secure delivery requires at least 1 file of cache per user. This is the fundamental one-time-pad cost of information-theoretic secrecy. Above this floor, coded caching's MAN gain still applies to the remaining memory . Secrecy is not free β unlike Wan-Caire demand privacy, it costs capacity.