From 4937a56421280e2a317a57f313e480d4cfeaef8e Mon Sep 17 00:00:00 2001
From: aamir <32578528+syedDS@users.noreply.github.com>
Date: Fri, 31 Jul 2026 11:37:08 -0400
Subject: [PATCH] Add recommendations for quantum data protection to QS01

---
 quantum-top-10/QS01_Harvest-Now-Decrypt-Later-Exposure.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/quantum-top-10/QS01_Harvest-Now-Decrypt-Later-Exposure.md b/quantum-top-10/QS01_Harvest-Now-Decrypt-Later-Exposure.md
index d8e1194..b2be625 100644
--- a/quantum-top-10/QS01_Harvest-Now-Decrypt-Later-Exposure.md
+++ b/quantum-top-10/QS01_Harvest-Now-Decrypt-Later-Exposure.md
@@ -17,6 +17,8 @@ Adversaries are already capturing encrypted traffic and stored ciphertext today,
 2. For data at rest, layer a PQC-protected encryption envelope over existing classical encryption for the highest-sensitivity datasets.
 3. Rotate symmetric data keys protected by quantum-vulnerable wrapping more frequently to reduce the volume exposed by any single recovered key.
 4. Reduce data retention where the business case allows - data not retained cannot be decrypted later.
+5. Physically or logically isolate critical data to prevent eavesdropping.
+6. Implement an allowed quantum protection mechanism, such as quantum cryptography, quantum networking, quantum key distribution, etc.
 
 **Example Attack Scenarios:**