Harvest Now, Decrypt Later

# Harvest Now, Decrypt Later

There's a strategy already in active use today that reads like a spy novel's premise and happens to be real: an adversary intercepts and stores encrypted traffic they cannot currently read, betting that a future quantum computer will let them decrypt it retroactively. Security researchers call it "harvest now, decrypt later," and it's one of the more unsettling ideas in this whole subject, because it means the theft already happened. The reading just hasn't caught up yet.

This inverts the usual shape of an espionage plot. A conventional heist story runs on urgency at the moment of the theft — steal the file, crack the safe, get out before the alarm sounds. Harvest-now-decrypt-later runs on patience instead: the theft is quiet, undramatic, possibly indistinguishable from ordinary network noise, and the payoff might be a decade away. The tension isn't in the taking. It's in not knowing which of today's encrypted secrets are sitting in someone else's storage, already lost, just not yet read.

That's a genuinely underused structure for fiction. A story could open with a "harvest" already having happened years earlier — a character's most guarded secret, encrypted and stolen long before the novel begins, now sitting in an adversary's archive with a due date attached to when it becomes readable. The suspense isn't "will they steal it." It's "how long do we have before the copy someone already has stops being useless to them" — a slow-fuse structure closer to a diagnosis with an unknown timeline than a traditional thriller countdown.

It also raises the stakes of the current, real standardization effort discussed elsewhere in this series: every year an organization delays switching to quantum-resistant encryption is another year of traffic being harvested today for reading tomorrow. The deadline isn't just Q-Day. It's now, for anything worth protecting for longer than a few years.