Study guides / ISC: Information Systems & Controls / Confidentiality, privacy & incident response
Confidentiality, privacy & incident response
ISC: Information Systems & Controls · quick review
Protecting information means encryption, hashing, data classification and minimization, and a tested incident response process from preparation through lessons learned.
The rules
- Symmetric encryption uses one shared key (fast, but key distribution is hard). Asymmetric encryption uses a public and private key pair: encrypt with the recipient's public key for confidentiality, sign with the sender's private key for authenticity.
- Hashing is one-way and fixed-length, and proves integrity. Digital signatures (a hash encrypted with a private key) give integrity, authenticity and non-repudiation.
- Privacy practices: data minimization, purpose limitation, retention and disposal schedules, masking or tokenization in non-production environments, and data classification.
- Event vs. incident: an event is any observable occurrence. An incident violates, or imminently threatens, security policy.
- NIST SP 800-61 life cycle: preparation, then detection and analysis, then containment, eradication and recovery, then post-incident activity (lessons learned).
Common traps
- Encrypting with the sender's private key doesn't keep a message confidential. Anyone with the public key can read it.
- Tokenization replaces a sensitive value with a surrogate that is mapped in a secure vault. Masking obscures values irreversibly for use.
- Preserve evidence before wiping systems. Eradication comes after containment and analysis.
How it's tested
Pick the right cryptographic tool, classify events and incidents, and order the incident response steps. Expect option list simulations.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson