Study guides / ISC: Information Systems & Controls / Availability & change management
Availability & change management
ISC: Information Systems & Controls · quick review
Covers keeping systems running and recoverable (business continuity, disaster recovery, backups) and keeping changes to systems authorized, tested and traceable.
The rules
- RPO = the maximum acceptable data loss, which sets backup frequency. RTO = the maximum acceptable downtime, which sets recovery capability.
- Backups: a full backup plus differentials (restore the full backup plus the latest differential) or a full backup plus incrementals (restore the full backup plus every incremental since). Keep copies offline or immutable, and test restores.
- Recovery sites: hot (fastest, most expensive), warm, cold (slowest, cheapest). Match the site to the RTO.
- Change management: request, approve, develop in a separate environment, test (including user acceptance), approve, migrate by someone independent of development, then document and review.
- Emergency changes: temporary elevated access, logging, and prompt after-the-fact review, approval and testing.
Common traps
- Backups kept on a network share connected to production can be encrypted by ransomware along with the production data.
- A business continuity plan covers the whole business. A disaster recovery plan focuses on restoring IT.
- Developers with access to production undermine program change controls, even if every change is approved.
How it's tested
Pick the right recovery metric, backup scheme or site, and evaluate change management controls, including emergency changes.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson