NIST SP 800-34 Revision 1: reprocessing time must be added to the RTO to stay within the MTD. Federal mission essential functions must meet an MTD of 12 hours or less (FCD-1). Check one system and price every hour past it.
| Template check RTO <= MTD (1 = passes) | - |
| Real outage: RTO + reprocessing, hours | - |
| Hours past the MTD | - |
| NIST check RTO + reprocessing <= MTD (1 = yes) | - |
| Longest RTO that still meets the MTD, hours | - |
| Downtime cost past the MTD | - |
| Downtime cost of the whole outage | - |
| Backups meet the RPO (1 = yes) | - |
| Backup gap beyond the RPO, hours | - |
| Records lost in a worst-case restore | - |
| Records lost beyond what the RPO allows | - |
Everything updates as you type. Nothing is uploaded. This runs in your browser.
The rule, as of October 14, 2026: NIST SP 800-34 Revision 1 (May 2010), section 3.2.1, says the RTO must ensure that the MTD is not exceeded, and the time it takes to reprocess data must be added to the RTO to stay within the MTD. RPO is not part of the MTD; it is how much data loss the process can tolerate, so the worst case is a disruption just before the next backup. Federal mission essential functions must meet an MTD of 12 hours or less (FCD-1, cited in SP 800-34). HIPAA covered entities must have a disaster recovery plan, listed as Required at 45 CFR 164.308(a)(7)(ii)(B). Downtime cost per hour is your own figure: lost sales, idle staff, overtime, penalties in your contracts. This is an arithmetic check, not legal or audit advice.