Control calendar
Cadence comes from policy — it is what an auditor measures. How often a collector samples is a separate thing, shown on the Collectors page.
| Control | Status | Cadence | Last | Next due | TSC | Description |
|---|---|---|---|---|---|---|
| IT-02:BC-01 | No evidence | Daily | — | — | A1.2 | Automated daily database backups; repositories version-controlled |
| IT-02:BC-02 | No evidence | Annual | — | — | A1.2 | RTO of 4 hours and RPO of 1 hour defined and documented |
| IT-02:BC-03 | No evidence | Annual | — | — | A1.2 | Recovery procedures documented; runbooks maintained; roles defined manual |
| IT-02:BC-05 | No evidence | Semi-annual | — | — | A1.2 | Semi-annual BC/DR readiness review with evidence captured manual |
| IT-02:BC-06 | No evidence | Annual | — | — | A1.3 | Annual formal BC/DR test: date, participants, results, corrective actions |
| IT-02:BC-08 | No evidence | Annual | — | — | A1.2 | All critical roles can operate remotely; no physical office dependency manual |
6 controls shown.