Data retention and destruction plan¶
Planning aid, not a certification or legally sufficient compliance document. Complete in an approved private documentation location. Never insert credentials, key material, or actual restricted records. Unknown required controls block approval.
- Project / nonsensitive identifier: [fill in]
- Prepared by / accountable owner: [fill in]
- Version / date / next review: [fill in]
- Classification and agreement references: [fill in]
- Approved evidence location: [fill in]
Copy inventory and obligations¶
| Copy / system | Owner | Class | Retention trigger / deadline | Hold or exception | Destruction method | Verification / evidence |
|---|---|---|---|---|---|---|
| Source / linkage keys | ||||||
| CyVerse objects / replicas | ||||||
| Trash / backups | ||||||
| VM volumes / swap / dumps | ||||||
| Snapshots / images | ||||||
| Notebook / spills / logs | ||||||
| Outputs / models | ||||||
| Credentials / key copies |
- Agreement/institutional retention basis and legal-hold reviewer: [fill in]
- Provider deletion timelines and retained exceptions: [fill in]
- Approved sanitation method and threat model: [fill in]
- Cryptographic erasure eligibility: all relevant key copies controlled, no retained plaintext, no recoverable keys, approved evidence: [fill in]
- Recovery obligations before destroying keys: [fill in]
- Verification owner, date, provider confirmations and custodian acceptance: [fill in]
File deletion or VM termination alone is not proof of sanitization.
Review and authorization¶
- Unresolved controls / remediation owner / due date: [fill in]
- Exceptions, approving authority, scope, and expiry: [fill in]
- Custodian decision / date / evidence reference: [fill in]
- Institutional decision / date / evidence reference: [fill in]
- Provider confirmation references: [fill in]
- Material changes requiring revalidation: [fill in]
For each control, record Supported, Configured, Verified, and Approved separately, with dates and evidence. Do not mark unknown as passed.