Study guide

10.3 Backup, Redundancy, Testing, and Drills

ISC2 Systems Security Certified Practitioner SSCP

Track your progress as you read

Finished sections get a check mark.

1 Introduction and Exam Overview

1.1 Current Exam Facts 1.2 Computerized Adaptive Testing, Scoring, and Retakes 1.3 Eligibility, Associate Pathway, Endorsement, and Maintenance

2 Ethics and Security Concepts

2.1 Comply with Codes of Ethics 2.2 Understand Security Concepts 2.3 Identify and Implement Security Controls

3 Functional Controls, Assets, and Change Management

3.1 Document and Maintain Functional Security Controls 3.2 Support and Implement the Asset Management Lifecycle 3.3 Support and Implement the Change Management Lifecycle

4 Security Awareness and Physical Security Operations

4.1 Support and Implement Security Awareness and Training 4.2 Collaborate with Physical Security Operations

5 Authentication Methods and Trust Architectures

5.1 Implement and Maintain Authentication Methods 5.2 Federated Access with OAuth2, SAML, and OpenID Connect 5.3 Understand and Support Internetwork Trust Architectures

6 Identity Lifecycle and Access Control Models

6.1 Support and Implement the Identity Management Lifecycle 6.2 Mandatory, Discretionary, and Role-Based Access Control 6.3 Rule-Based, Attribute-Based, and Privileged Access Management

7 Risk Management, Visibility, and Legal Concerns

7.1 Risk Management Concepts and Treatment 7.2 Risk Visibility, Reporting, and Threat Intelligence 7.3 Legal and Regulatory Concerns

8 Assessments, Monitoring, and Analysis

8.1 Security Assessments and Vulnerability Management 8.2 Operate and Monitor Security Platforms 8.3 Analyze Monitoring Results

9 Incident Response and Forensic Investigations

9.1 Incident Response: Preparation, Detection, Analysis, and Escalation 9.2 Containment, Eradication, Recovery, and Lessons Learned 9.3 Understand and Support Forensic Investigations

10 Business Continuity and Disaster Recovery

10.1 Business Continuity and Emergency Response 10.2 Disaster Recovery and Restoration Metrics 10.3 Backup, Redundancy, Testing, and Drills

11 Cryptography Foundations

11.1 Reasons and Requirements for Cryptography 11.2 Hashing, Salting, Symmetric, Asymmetric, and ECC 11.3 Digital Signatures, HMAC, Algorithm Strength, and Cryptanalysis

12 Secure Protocols and Public Key Infrastructure

12.1 Understand and Implement Secure Protocols 12.2 Understand Public Key Infrastructure

13 Networking Fundamentals, Attacks, and Access Controls

13.1 Understand and Apply Fundamental Concepts of Networking 13.2 Understand Network Attacks and Countermeasures 13.3 Manage Network Access Controls

14 Network Security Operations, Wireless, and IoT

14.1 Manage Network Security 14.2 Operate and Configure Network-Based Security Appliances and Services 14.3 Secure Wireless Communications 14.4 Secure and Monitor Internet of Things

15 Malware, Malicious Activity, and Endpoint Security

15.1 Identify and Analyze Malicious Code 15.2 Malicious Activity, Social Engineering, and Behavior Analytics 15.3 Implement and Operate Endpoint Device Security

16 Mobile, Cloud, and Virtual Environments

16.1 Administer and Manage Mobile Devices 16.2 Cloud Security: Deployment, Service Models, and Shared Responsibility 16.3 Cloud Legal, Regulatory, and Third-Party Requirements 16.4 Operate and Maintain Secure Virtual Environments

10.3 Backup, Redundancy, Testing, and Drills

Key Takeaways Explain This Topic AI

RAID and other local redundancy survive a disk fault. They are not backups. Ransomware, deletion, and a site fire still need a separate restore copy.

Full, incremental, and differential backups restore differently: last full plus every incremental, or last full plus the latest differential.

Keep multiple copies on more than one media type with at least one offsite, plus an offline or immutable generation so ransomware cannot encrypt the only restore path.

Do not restore last night's backup if that job ran after encryption started. Use the last known-clean copy and scan it in isolation.

A tabletop validates roles and decisions. Measuring Restore Time Objective requires a disaster recovery exercise that actually restores. Schedule tests so you do not create a payday outage in the name of proof.

Last updated: August 2026

Backup versus redundancy

The SSCP outline pairs Backup and redundancy implementation with Testing and drills (playbook, tabletop, disaster recovery exercises, scheduling). Backups are how you hit RPO . Tests are how you prove RTO . Mixing backup with redundancy is the trap that fails both the exam and the ransom note.

Backup is a copy you can restore after data is destroyed, encrypted, corrupted, or deleted — preferably a copy the threat cannot also destroy. Redundancy (a second power supply, Redundant Array of Independent Disks (RAID) , a clustered node, a second network path) keeps a service available through a component failure.

RAID is not a backup. RAID-5 or RAID-6 can survive one or two disk failures. It does not survive ransomware that encrypts every disk in the array, an administrator who deletes a volume, a fire in the same rack, or silent corruption that is then rebuilt onto the parity disks. If the only copy is another disk in the same server, you have redundancy, not a restore path.

  • Mechanism Protects against Fails against
  • RAID / local disk mirror Disk hardware fault Ransomware, deletion, site disaster, many firmware bugs

Synchronous replication to a peer Site loss if the peer is far enough and independent Logical corruption and ransomware if every write is replicated immediately

Backup (offline, immutable, or offsite) Deletion, many disasters, ransomware if the copy is unreachable or locked Unrestorable media, untested catalogs, jobs taken after infection

Snapshots on the same array Quick rollback of mistakes Array failure; many ransomware families that delete or encrypt snapshot stores

Use redundancy and backups. A stem that treats RAID-6 plus a hot spare as offsite backup is wrong even if the array is healthy.

Replication is not automatically a backup either. A mirrored volume in the same site is still one fire. A synchronous replica that instantly copies encrypted files gives you two encrypted copies and an excellent RPO of malware. Delayed or versioned replication, plus an offline generation, is how you keep a clean point in time.

Backup types and how you actually restore them

Type What is copied Restore method Window and storage Trap

Full Everything selected One set Slowest backup, simplest restore Teams skip fulls to save capacity, then cannot restore incrementals

Incremental Changes since the last backup of any type Last full plus every incremental after it Fastest backup, slowest and most fragile restore One missing or corrupt incremental breaks the chain

Differential Changes since the last full Last full plus the latest differential Medium backup, simpler restore than incremental Differentials grow until the next full

Synthetic full / incrementals forever Product-specific merge Follow the vendor runbook Convenient when it works Still not a backup if it lives only on the production array

Restore math. Full on Sunday. Incrementals Monday through Thursday. Thursday-night ransomware. Restore = Sunday full + Monday + Tuesday + Wednesday + Thursday incrementals — unless Thursday's job ran after encryption. Then you stop at the last known-clean incremental and accept the RPO miss. Differentials: Sunday full + Thursday's differential only.

Rotation schemes (grandfather-father-son and similar) keep multiple generations so you can reach back past last night. That matters for ransomware with dwell time: the encryptor may already have been inside last night's successful job. A single overwrite-every-night disk is an RPO of 24 hours and a single point of failure.

Implementation details that show up in stems:

Encrypt backup media; store keys where destroying the tape does not destroy the only key, and where stealing the key does not unlock every vault.

Document what is not in the job (temp, scratch, a shadow database an app owner added without telling IT).

Databases and domain controllers need application-consistent backups (quiesce, Volume Shadow Copy, vendor agent). A crash-consistent snapshot may not replay cleanly.

Cloud snapshots in the same account are not offsite. Copy to another account or region with a separate identity .

The backup service account must not be ordinary domain admin. MFA, monitored use, and a unique vault identity make ransomware's favorite second victim harder to take.

Protect the catalog. A perfect tape you cannot index is a box of rust.

A widely taught operations pattern is 3-2-1 : at least three copies of data, on two different media types, with one offsite. Ransomware-era practice adds an immutable or air-gapped generation and a verified restore (sometimes marketed as 3-2-1-1-0). ISC2 does not publish a branded slogan you must name. Knowledge area 4.3 is testing whether you know that online-only backups get encrypted too .

  • Control What it does in a ransomware event
  • Offline / air-gapped (tape pulled, disk powered down, vault) Attacker cannot reach it over the network

Immutable (object lock, write-once media, vendor retention lock) An attacker with backup-admin credentials cannot delete or encrypt that generation until retention expires

Offsite / other region / other cloud account Survives the building; if identity is split, may survive a compromised tenant

  • Separate backup identity Backup is not the same as domain admin; use is logged
  • Restore testing Proves the catalog and media actually work

Online backup servers on the same VLAN as the file server are a second victim. Knowledge area 4.1 already taught you not to recover from an infected generation. This section is the design so a clean generation exists: immutable copies, delayed replication so corruption does not land instantly, and isolation of the backup control plane.

Restoring from last night's infected backup

Scenario. Last night's backup of FILESERVER01 finished at 02:00. Encryption started at 01:10. The job is marked successful because files were copied — including the encryptor and the encrypted share. Restoring that job meets a 24-hour RPO on paper and re-infects production.

An immutable Saturday copy from before initial access still exists in object storage with retention lock. The SSCP restores Saturday , to an isolated network, scans it, rotates any secrets baked into the image, and only then reconnects a share. If no such copy exists, the backup program failed before the incident. Meeting RPO with malware is not meeting RPO.

Select the restore point before initial access , not before the ransom note. Dwell time of days is common. The last successful job is a status icon, not a cleanliness certificate. After restore, watch endpoint detection longer than it feels necessary; then record actual data loss against RPO for the lessons-learned meeting.

Testing and drills

The outline's last 4.3 bullet is Testing and drills (e.g., playbook, tabletop, disaster recovery exercises, scheduling) . An untested BCP or DRP is a hypothesis. Tests find missing DNS, expired certificates, backup catalogs that do not restore, and a hot site whose switch still has last year's VLAN list.

Test type What people actually do What it proves What it does not prove

Checklist / walkthrough Read the plan, update phone numbers The document still matches org charts That restore works

Playbook drill Follow a technical runbook on a real or lab system (restore one database, fail a VLAN) A specific procedure can be executed Whole-site endurance and user cutover

Tabletop Facilitated discussion of a scenario; no production failover Decision paths, roles, gaps in communication and authority That hardware, bandwidth, or backups work; cannot measure RTO

Simulation Dummy data or an isolated environment under timed conditions Muscle memory without touching production Full production dependencies

Parallel test Bring up the DR environment and process a copy of work while production stays up The environment can run the workload Production DNS, client cutover, and user confusion

Full interruption / cutover / disaster recovery exercise Production is failed over or shut down for real The only live proof that RTO and RPO hold You can still fail if you never schedule it, or if you test only at 02:00 Sunday with the A-team

Playbooks are the technical scripts: commands, ticket queues, who has break-glass, in which order you restore identity before payroll. Tabletops exercise decisions: who declares, who talks to contractors, whether you isolate the backup VLAN. Disaster recovery exercises exercise systems. You need all three. A PDF nobody has opened is not support for 4.3.

Tabletop versus full failover is an exam favorite.

Scenario. The CISO wants proof we can meet the 8-hour payroll RTO. The team runs a two-hour tabletop. Everyone agrees the warm site should work. A tabletop cannot measure RTO . It can prove that the payroll director knows who declares a disaster, that the out-of-band bridge number is current, and that legal knows when to call the processor. Measuring eight hours requires a disaster recovery exercise that actually restores payroll — preferably a parallel test first, then a scheduled cutover. Skipping to a surprise full interruption on a Friday payday is how you create a disaster in order to test for one.

Scheduling

Scheduling is on the outline because a test at the wrong time is either theater or an outage.

Do not schedule a full payroll failover on the Thursday before Friday contractor pay unless the BIA and leadership accept that risk in writing.

Do schedule some tests during business-like hours. A 02:00 Sunday restore with the A-team on the bridge does not prove a Tuesday 14:00 disaster with the B-team and a stuck MFA vendor.

Announce tabletop and parallel tests. Surprise belongs to detection drills, not to dropping production DNS.

After-action: update the playbook, update the BIA if MTDs changed, and put the next test on the calendar. A test with no findings is usually a test that was not trying.

Test after major changes (new identity provider, datacenter move, backup-product swap), not only once a year. ISC2 does not publish a universal SSCP-required interval. Follow policy, contracts, and regulators that actually apply to that organization.

Scope tests the way you scoped the BIA. Restoring a wiki proves nothing about payroll. Restoring payroll without DNS, certificates, and the time-clock interface proves a server boots, not that contractors get paid.

Restore sequence that ties 4.3 together

Life safety and occupant emergency if the site is unsafe.

Declare using BIA criteria; activate crisis management and communications.

Start BCP interim processing (paper payroll, sister warehouse).

Select a known-clean backup generation that meets RPO as closely as possible without restoring malware.

Restore at the site whose design meets RTO, on an isolated network if this is also an incident.

Validate at the application level — a test pay cycle, not a ping.

Complete WRT (clerks catch up; reconcile paper).

Record actual time against RTO, RPO, and MTD; feed lessons into the next drill.

When a CAT stem offers RAID as the offsite copy, refuse it. When it offers last night's successful job taken during encryption, refuse it. When it offers a tabletop as proof of an 8-hour RTO, name the test that actually restores.