Fault Tolerance & Cybersecurity - Complete Interactive Lesson
Part 1: Core Concepts
🛡️ Fault Tolerance & Security
Part 1 of 7 — Redundancy, Encryption, and Network Security
Fault Tolerance
Fault tolerance is the ability of a system to continue operating when a component fails.
Redundancy
The primary method for achieving fault tolerance is redundancy — having backup components or paths.
| Type | Description | Example |
|---|---|---|
| Path redundancy | Multiple routes between nodes | Internet routing around a failed link |
| Data redundancy | Multiple copies of data | Cloud backups, RAID drives |
| Hardware redundancy | Backup equipment | Redundant servers, power supplies |
Internet Redundancy
A ---- B ---- C
| | |
D ---- E ---- F
If the link between B and C fails, data can route A → B → E → F → C or A → D → E → F → C. Multiple paths ensure no single failure brings down the network.
🔑 The Internet was designed with redundancy so that no single point of failure can take down the entire network. Packets automatically reroute around failed links.
Concept Check 🎯
Cybersecurity Fundamentals
Encryption
Encryption transforms readable data (plaintext) into unreadable data (ciphertext) to protect it from unauthorized access.
| Type | Keys | Speed | Use Case |
|---|---|---|---|
| Symmetric | One shared key for encrypt and decrypt | Fast | Encrypting stored data |
| Asymmetric | Public key (encrypt) + Private key (decrypt) | Slower | Secure communication, HTTPS |
How HTTPS Uses Both
- Browser gets web server public key (asymmetric)
- Browser encrypts a session key with the public key
- Server decrypts session key with its private key
- Both sides use the session key (symmetric) for fast communication
Common Threats
| Threat | Description |
|---|---|
| Phishing | Fake emails/sites tricking users into giving up passwords |
| Malware | Software designed to damage or gain unauthorized access |
| DDoS | Distributed Denial of Service — flooding a server with traffic |
| Man-in-the-middle | Attacker intercepts communication between two parties |
| Keylogger | Records everything typed, capturing passwords |
| Ransomware | Encrypts user files and demands payment to unlock |
Applied Recall ✍️
-
Having multiple backup paths or components so a system continues working after a failure is called _______.
-
Encryption that uses one shared key for both encryption and decryption is called _______ encryption.
-
An attack that tricks users into revealing passwords through fake emails or websites is called _______.
Security Classification 🔍
AP Exam Strategy: Fault Tolerance & Security
- Redundancy is the #1 fault tolerance mechanism — multiple paths and backups
- Know symmetric (one key, fast) vs asymmetric (two keys, secure key exchange)
- HTTPS uses BOTH: asymmetric for initial handshake, symmetric for ongoing communication
- Know common attacks: phishing, malware, DDoS, man-in-the-middle
- A single point of failure means the system is NOT fault tolerant at that point
- More connections in a network = more redundancy = more fault tolerant
AP-Style Application 🎯
Part 2: Key Processes
🛡️ Fault Tolerance & Security
Part 2 of 7 — Key Processes
Fault Tolerance: Working Despite Failures
A fault-tolerant system continues operating correctly when a component fails. The key idea: redundancy plus a way to detect and recover from failures.
| Technique | How it tolerates faults |
|---|---|
| Redundancy | Multiple copies of data or compute. |
| Replication | Same data in many locations. |
| Failover | Automatic switch to a backup. |
| Retries | Try again when a request fails. |
| Graceful degradation | Reduce functionality instead of crashing. |
Concept Check 🎯
Why The Internet Survives Failures
The original Internet design (1960s ARPANET) assumed parts of the network would fail. Packet switching + dynamic routing means traffic can flow around broken links automatically.
| Failure | Mitigation |
|---|---|
| Cable cut | Routers find alternate paths. |
| Server crash | Load balancer routes to a healthy peer. |
| Region outage | Multi-region deployment. |
| Disk failure | RAID + offsite backup. |
Backups Are Different From Replication
| Concept | Purpose |
|---|---|
| Replication | Live copies for high availability. |
| Backup | Snapshot in time for recovery from corruption / mistake. |
If a bug DELETES data and replicates the deletion to all replicas, only a backup saves you.
A Tiny Example: Retries With Backoff
attempt ← 1 REPEAT WHILE attempt ≤ 5: result ← TRY_REQUEST() IF result.success THEN STOP WAIT(2 ^ attempt seconds) // exponential backoff attempt ← attempt + 1
Exponential backoff prevents retry storms from overwhelming a recovering service.
Applied Recall ✍️
-
Tolerating component failure typically requires _______ — extra capacity / copies.
-
A system that reduces functionality instead of crashing during partial failure is showing _______ degradation.
-
A disk-failure-resistant arrangement of multiple disks is called _______.
Targeted Practice 🔍
AP Exam Strategy: Fault Tolerance
- Redundancy + failover = canonical fault-tolerance answer.
- Distinguish replication (live) from backups (point-in-time).
- The Internet itself is a giant fault-tolerant system.
AP-Style Application 🎯
Part 3: Patterns & Examples
🛡️ Fault Tolerance & Security
Part 3 of 7 — Patterns & Examples
Security Has Three Goals: CIA
| Goal | Meaning |
|---|---|
| Confidentiality | Only authorized parties can read. |
| Integrity | Data isn't altered without detection. |
| Availability | The service keeps responding. |
Different threats target different goals; defenses are different for each.
Concept Check 🎯
Common Threats And Defenses
| Threat | Defense |
|---|---|
| Eavesdropping | TLS / encryption in transit. |
| Tampering | Digital signatures, message-authentication codes (MAC). |
| Phishing | User awareness, MFA, anti-phishing tools. |
| Malware | Updates, sandboxing, antivirus, code signing. |
| DDoS | Rate limiting, CDNs, scrubbing. |
| SQL injection | Parameterized queries, input validation. |
| Credential theft | MFA, password managers, breached-password checks. |
Symmetric vs. Asymmetric Encryption
| Style | Key |
|---|---|
| Symmetric | Same key encrypts and decrypts (AES). |
| Asymmetric | Public key encrypts; private key decrypts (RSA, ECC). |
Real systems use both: asymmetric to safely exchange a symmetric key, then symmetric for bulk traffic.
Hashing Vs Encryption
| Property | Hash | Encryption |
|---|---|---|
| Reversible? | No | Yes (with key) |
| Use | Verify integrity, store password hashes | Confidentiality |
A password should be hashed (with salt + slow algorithm), not encrypted.
Applied Recall ✍️
-
The "C" in CIA stands for _______.
-
Encryption that uses one shared key is called _______.
-
A one-way function that produces a fixed-size digest is called a _______.
Targeted Practice 🔍
AP Exam Strategy: Security Basics
- CIA: confidentiality / integrity / availability.
- Match defense to threat.
- Hashes ≠ encryption — passwords get hashed.
- Real systems use symmetric + asymmetric together.
AP-Style Application 🎯
Part 4: Connections & Interactions
🛡️ Fault Tolerance & Security
Part 4 of 7 — Connections & Interactions
Security & Fault Tolerance Connect Across CSP
| Connection | Why |
|---|---|
| Security ↔ Networks | Most attacks come over the network. |
| Fault tolerance ↔ Systems | Systems fail; designs must adapt. |
| Security ↔ Data | Data must be protected throughout its lifecycle. |
| Security ↔ Impact | Breaches have human consequences. |
Concept Check 🎯
Defense In Depth
No single defense is enough. Layer them:
| Layer | Defense |
|---|---|
| Perimeter | Firewall, DDoS scrubbing. |
| Network | TLS, segmentation. |
| Host | Patching, hardening. |
| App | Input validation, least privilege. |
| Data | Encryption-at-rest, backups. |
| Identity | MFA, strong auth. |
| Process | Code review, secure SDLC. |
If one layer fails, others still hold.
Threat Modeling
Ask: who would attack this, why, and how? Common categories: nation-states, organized crime, opportunistic attackers, disgruntled insiders, accidental damage.
Security Is A Process, Not A Product
Tools alone don't make a system secure. Patching, monitoring, and incident response matter as much as initial design.
Applied Recall ✍️
-
Layering multiple security defenses is called defense in _______.
-
A formal exercise to ask "who would attack this and how" is called _______ modeling.
-
A system's ability to keep responding during partial failure is _______ tolerance.
Targeted Practice 🔍
AP Exam Strategy: Cross-Topic Security
- Defense in depth — layered defenses.
- Threat modeling identifies WHO and HOW.
- Backups + replication + monitoring + response = comprehensive resilience.
AP-Style Application 🎯
Part 5: Change Over Time
🛡️ Fault Tolerance & Security
Part 5 of 7 — Change Over Time
How Security & Fault Tolerance Have Evolved
| Era | Defining shift |
|---|---|
| 1990s | Anti-virus, basic firewalls. |
| 2000s | TLS adoption; widespread cyberattacks. |
| 2010s | Cloud-scale DDoS, ransomware, MFA mainstream. |
| 2020s | Supply-chain attacks, AI-assisted phishing, post-quantum prep. |
Concept Check 🎯
Notable Modern Shifts
| Shift | Effect |
|---|---|
| Cloud everywhere | Big providers handle base infra; devs share responsibility. |
| Zero trust | Don't trust any network; verify every request. |
| Ransomware | Backups + segmentation + plan = recoverability. |
| AI-assisted attacks | Phishing/spam quality is rising. |
| Open-source dependencies | Strong upside; supply-chain risk. |
"Security Through Obscurity" Doesn't Work
Hiding the algorithm isn't a substitute for sound design. Strong cryptography is public — its security depends on the key, not the secrecy of the method.
Applied Recall ✍️
-
A model that does NOT trust any network and verifies every request is called _______ trust.
-
An attack on a popular library to compromise its many downstream users is a _______-chain attack.
-
Cryptography designed to resist future quantum-computer attacks is called _______-quantum.
Targeted Practice 🔍
AP Exam Strategy: Security Evolution
- Modern attackers exploit supply chain, not always users directly.
- Zero trust is the dominant new architecture.
- AI changes the threat landscape (phishing quality up).
AP-Style Application 🎯
Part 6: Problem-Solving Workshop
🛡️ Fault Tolerance & Security
Part 6 of 7 — Problem-Solving Workshop
Fault Tolerance & Security Workshop
Concept Check 🎯
Worked: Designing An Outage-Resistant Service
| Layer | Plan |
|---|---|
| Servers | Multiple instances behind a load balancer. |
| Region | Multi-region with automatic DNS failover. |
| Data | Replicated DB + nightly backups + retention plan. |
| Code | Blue/green or canary deploys to enable rollback. |
| Monitoring | Alerts on errors, latency, saturation. |
| People | On-call rotation + runbooks + post-incident review. |
Worked: A Phishing Triage
- Don't click.
- Check sender domain (often misspelled).
- Hover URLs to see the actual destination.
- Verify out-of-band (call the company at a known number).
- Report to IT / mark as phishing.
Worked: Choosing Authentication
| Use case | Recommendation |
|---|---|
| School portal | Username + password + MFA |
| API for partners | OAuth / API key + rate limits |
| Internal admin | SSO + hardware-key MFA + role-based access |
| Public read-only | No auth, rate-limit only |
Applied Recall ✍️
-
A deployment style that gradually rolls out to a small fraction first is called a _______ release.
-
A document teammates follow during an outage is called a _______.
-
After an incident, the team usually runs a _______-mortem to learn from it.
Targeted Practice 🔍
AP Exam Strategy: Workshop
- Plan for failure: redundancy + monitoring + runbooks + drills.
- Layered authentication based on use case.
- Canary releases reduce blast radius of bad changes.
AP-Style Application 🎯
Part 7: AP Review
🛡️ Fault Tolerance & Security
Part 7 of 7 — AP Review
AP Exam Recap — Fault Tolerance & Security
Concept Check 🎯
Final Vocab
| Term | Definition |
|---|---|
| Fault tolerance | Continues operating during failures. |
| Redundancy / replication / failover | Mechanisms enabling fault tolerance. |
| Backup | Point-in-time data snapshot. |
| CIA | Confidentiality, Integrity, Availability. |
| Symmetric / asymmetric encryption | One key vs. key pair. |
| Hash | One-way digest. |
| MFA | Multi-factor authentication. |
| Phishing / DDoS / ransomware | Common threats. |
| Defense in depth | Layered defenses. |
| Zero trust | Verify every request. |
| Supply-chain attack | Compromise a trusted dependency. |
Common Pitfalls
- Confusing replication and backup.
- Storing passwords in plaintext or reversible encryption.
- Treating security as a one-time install.
- No incident plan / runbooks / drills.
- Trusting the network instead of verifying each request.
Applied Recall ✍️
-
The "I" in CIA stands for _______.
-
An attack that overwhelms a service to deny availability is a _______ attack.
-
A second proof of identity beyond the password is the second _______.
Targeted Practice 🔍
Final Exam Tips
- CIA framing for security questions.
- Replication ≠ backup.
- Defense in depth, MFA, TLS, hashed passwords.
- Process matters: patches, monitoring, drills, post-mortems.
AP-Style Application 🎯