FTA-002: Corruption Replicated Into Untested Backups ¶
1 Status ¶
| Date | Status | |
|---|---|---|
| 06-07-2026 | Identified | |
| 07-07-2026 | Analysed | |
| ▶ | 08-07-2026 | Mitigating |
2 Top Event ¶
Permanent loss of user data (TOP-1)
3 Minimal Cut Set ¶
{E2, E5} — silent write corruption replicated into backups whose restore was never tested
4 Description ¶
A record is corrupted on write without any error and the corruption is faithfully replicated into every backup generation. Because a restore has never been exercised, the backups' unusability is discovered only at the moment they are needed.
5 Severity ¶
6 Likelihood ¶
7 Mitigation ¶
Verify every completed backup by restoring it to a scratch area and comparing record checksums against the primary copy, so corrupted backups are detected at backup time, not at restore time.
8 Residual Severity ¶
9 Residual Likelihood ¶
10 Affected Documents ¶
| # | Proposed Text | Req-ID |
|---|---|---|
| 1 | The software shall verify every completed backup by restoring it to a scratch area and comparing record checksums against the primary copy. | REQ-020 |
11 Monitoring ¶
Restore-verification failures are counted per month; any non-zero count reopens the analysis.