Recovery Point Objective (RPO)
The maximum amount of data that can be lost after a disruption, expressed as a time interval (e.g., the last hour of data).
RPO answers the question: how far back in time must data be restored for the loss to remain acceptable? An RPO of one hour means you can afford to lose at most one hour of work, which means backups must be created at least every hour.
RPO is set per process on the basis of a Business Impact Analysis (BIA), in the same way as RTO. The distinction is simple: RTO is the time to recover; RPO is the amount of data that can be lost.
These two numbers together determine the cost and architecture of your business continuity solution. An ambitious RPO without the budget for frequent backups is a commitment that will not hold when a real disruption occurs.
In practice: see the relevant RealSec module.
Compliance that connects.
Terms are the map. RealSec ties them to processes, systems and vendors in one engine.