Policy 20  

Backup & Business Continuity Policy
PCI DSS Req 12.10 (contingency)  ·  the rule Revique must follow
← All 21 policies
This page is the rule, not the implementation. It states what Revique must do, at or above the PCI DSS minimum. How Revique actually does it today — the real AWS configuration, the current values, and where an auditor logs in to verify them — is in Procedure 20. Values shown as [X] are placeholders still to be set.

Purpose

To ensure Revique can recover data and restore operations after a disruption or disaster.

Scope

Applies to all critical systems and data required to operate Revique services.

Policy statements

Each statement below is mandatory. The bolded must marks the obligation.

1Backups of critical data must be performed on a defined schedule.
2Backups must be encrypted and access-controlled.
3A documented disaster recovery / business continuity plan must be maintained.
4Backup restoration must be tested at least [X] and results documented.
5Recovery objectives (RTO/RPO) must be defined for critical systems.

Roles & responsibilities

RoleResponsibility
Security OfficerOwn the continuity plan and testing.
DevOps / ITPerform backups and restoration tests.

Enforcement

This policy is issued under the authority of Policy 01 — Information Security Policy and is mandatory for everyone in scope. Compliance is verified through the controls and evidence described in the linked procedure. Failure to comply may result in withdrawal of access and disciplinary action. This policy is reviewed at least annually, or sooner on significant change.

⚙️See the Procedure for this policyHow Revique implements this rule today, the current values, the gaps, and the auditor verification path→
Revique security documentation  ·  generated 2026-08-13  ·  all identifiers masked  ·  AWS facts collected read-only on 2026-08-13
Policies define the rule; procedures describe the implementation and how to verify it.