TechclickCISSP Prep
☰

CISSP cheat sheet · Domain 7 · 13% of exam

Security Operations

Running security day to day: investigations and evidence, logging and monitoring, incident response, change and patch management, backups, recovery sites and disaster recovery.

Rule cards

Incident responseDetect → Respond → Mitigate (contain) → Report → Recover → Remediate (root cause) → Lessons learned. Same incident repeating = remediation failed; many different incidents = weak preparation.
NIST SP 800-61Preparation → Detection & Analysis → Containment, Eradication & Recovery → Post-incident activity (Rev. 3 aligns with CSF 2.0).
ForensicsIdentify → Preserve → Collect → Examine → Analyze → Present → Decide · RAM before disk · never work on the original (bit image + write blocker + hash) · chain of custody throughout.
Order of volatilityCPU registers/cache → RAM → swap → disk → remote logs → archival media.
EvidenceRelevant + material + competent · best evidence = original · parol evidence = the written contract wins · hearsay ✗ except business records (logs).
BackupsRestore speed: Full > Differential > Incremental (backup speed is the reverse) · incremental resets the archive bit, differential does not · 3-2-1 rule · RAID is not a backup.
RAID0 striping (no redundancy) · 1 mirroring · 5 striping + parity (1 disk) · 6 double parity (2 disks) · 10 mirror + stripe.
Recovery sitesMirror = minutes · Hot = hours · Warm = days · Cold = weeks · recovery team → alternate site (critical first) · salvage team → repairs primary (least critical moves back first).
MetricsRPO = data loss tolerance · RTO = time to restore · WRT = time to verify · MTD = RTO + WRT · MTBF = repairable · MTTF = non-repairable · MTTR = repair time.
Ops controlsLeast privilege · need to know · SoD (preventive) · job rotation / mandatory vacation (detective) · two-person control for critical tasks.
Change managementRequest → Impact assessment → Approve → Test → Notify → Implement → Validate → Document. Emergency changes are still documented afterwards.
Vulnerability managementDetect → Validate (false positive?) → Prioritise by risk → Remediate · no patch available → compensating control (WAF / virtual patching).
e-Discovery (EDRM)Governance → Identify → Preserve (legal hold) → Collect → Process → Review → Analyze → Produce → Present.

Hard words made simple

TermSimple meaningExample / analogyExam hook
ContainmentStop the spreadIsolate the infected serverFirst action once an incident is confirmed
RemediationFix the root causePatch the exploited bugAfter recovery
Order of volatilityCollect what disappears fastest firstRAM before diskNever pull the plug first
Chain of custodyRecord of who held evidence, when and whyCourier tracking for evidenceGaps = inadmissible
Write blockerDevice that prevents changes to the original disk—Preserves integrity
Legal holdOrder to keep data for litigationDo not delete those emailsOverrides retention
SpoliationDestroying evidenceDeleting held dataIllegal
SIEM / SOARCollect + correlate logs / automate response playbooksAlert → host auto-isolatedAutomated response → SOAR
Threat huntingProactively search for hidden attackersAssume breachProactive, not alert-driven
SandboxIsolated place to detonate suspicious filesAttachment tested before deliveryUnknown malware
HoneypotDecoy system to attract attackersFake vulnerable serverEnticement, legal
Electronic vaulting / remote journalingBulk backups sent off-site / transaction logs sent continuously—Journaling = transaction level
Parallel testDR site runs alongside productionBoth run; compare resultsCritical system, no disruption
Non-adversarial eventDisruption with no attackerPower cut, flood, hardware failure→ DR / BCP thinking
UPS vs generatorBattery bridge (instant) vs fuel power (starts after outage)Inverter vs diesel gensetZero downtime → UPS

Ready for the full bank?

2,000+ explained questions, timed mocks and a CAT simulator that behaves like the real exam.