The four variables
Where the data can actually be captured
The second variable: harvestability — the concrete surfaces where an adversary could plausibly capture protected data today.
5 min read
What you'll be able to do
- Define harvestability and explain why it gates HNDL exposure even when data is long-lived.
- List the main capture surfaces: transit, backups and archives, third parties, logs, and replicas.
- Explain why "not harvestable" ends the HNDL analysis for a given data flow.
Confidentiality lifetime answers how long it matters. Harvestability answers whether an adversary could plausibly get a copy today. Both have to be true for HNDL risk to exist — a data flow that cannot realistically be captured is not HNDL-exposed, regardless of how sensitive or long-lived the data is.
| Surface | What makes it capturable |
|---|---|
| Network transit | Internet-exposed traffic can be captured by a passive collector anywhere on the path; internal-only traffic needs a foothold inside the network first. |
| Backups and archives | Often copied to lower-security storage, retained far longer than the live system, and reviewed far less often. |
| Third parties and processors | Any vendor, partner, or processor that receives or stores the data extends the set of places it can be captured from — the data is only as protected as the weakest custodian. |
| Logs and telemetry | Frequently capture more of the original payload than intended, and are often held to a lower retention and access standard than the system they describe. |
| Replicas and data lakes | Copies made for analytics, disaster recovery, or search often outlive and out-scope the access controls on the source system. |
Internet-exposed traffic and durable copies — backups, logs, replicas, anything a third party holds — are the surfaces worth checking first. Internal-only, ephemeral, never-copied data is the one combination that is genuinely hard to harvest.
Harvestability narrows the field. The next variable asks, for whatever is left, exactly which cryptography stands between an adversary and the data.
Marking a lesson complete only updates this browser.