Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/43 ▾
  1. 1.Security Principles & Control Types0/5
    1. The CIA triad: confidentiality, integrity and availability
    2. Identification, authentication, authorization and accounting
    3. Authentication factors and true multifactor
    4. Classifying controls by category and by function
    5. Risk transfer, guidelines and due care in this domain
  2. 2.Risk, Policy Hierarchy & Ethics0/4
    1. Threats, vulnerabilities, likelihood and impact
    2. The risk management lifecycle and the four treatments
    3. Laws, frameworks and the policy document hierarchy
    4. Due care, due diligence and the ISC2 Code of Ethics
  3. 3.Governance, Risk & Compliance0/4
    1. What GRC is for, and who is accountable
    2. Frameworks, standards and where obligations come from
    3. Key metrics, KPIs and key risk indicators
    4. Dashboards, scorecards, reports and AI risk indicators
  4. 4.Continuity, Disaster Recovery & Awareness0/4
    1. Redundancy, business continuity and disaster recovery
    2. Business impact analysis, RPO, RTO and alternate sites
    3. Backup types, offline copies and test restores
    4. Security awareness, culture and AI-powered phishing
  5. 5.Identity Lifecycle Management0/4
    1. Roles definition and provisioning new accounts
    2. Access reviews, movers and privilege creep
    3. Deprovisioning leavers and non-human identities
    4. Identity frameworks and tools: SSO, federation, SCIM, PAM and IGA
  6. 6.Logical Access Controls & Models0/4
    1. Least privilege and need-to-know
    2. Separation of duties, dual control and job rotation
    3. Subjects, objects and discretionary access control
    4. MAC, RBAC, rule-based and attribute-based access control
  7. 7.Network Security Concepts0/5
    1. The OSI and TCP/IP models
    2. IPv4 private addresses, NAT and IPv6
    3. VPNs: what they protect and what they do not
    4. Firewalls, ports and applications
    5. Wireless, Bluetooth, ICS and IoT devices
  8. 8.Network Architecture & Cloud Security0/4
    1. Network segmentation, firewall zones and VLANs
    2. Defense in depth and zero trust
    3. Cloud characteristics and deployment models
    4. Service models and the shared security model
  9. 9.Data Security & Security Operations0/5
    1. Data classification, labeling, data states and masking
    2. Retention and media sanitization
    3. Symmetric and asymmetric encryption, hashing and signatures
    4. Logging, monitoring and event triage
    5. Threat actors, threat intelligence and threat frameworks
  10. 10.Incident Response, Assets & Testing0/4
    1. The incident response plan, team and exercises
    2. The incident response life cycle
    3. Asset lifecycle, configuration and change management
    4. Security testing: teams, scans, application tests and physical tests
Saved in this browser. Move it to another device →
← Data Security & Security Operations

Chapter 9 · Lesson 4 of 5

Logging, monitoring and event triage

1 min read

Logging is a detective control. It records who did what, where and when, so a team can detect, investigate and rebuild events afterward. It prevents nothing by itself, so it works alongside preventive controls. Two practices make logs trustworthy.

First, every system syncs its clock to the same trusted time source; otherwise records from different servers cannot be put in the right order. Second, logs are forwarded at once to a central, write-once store with restricted access, so an attacker with admin rights on one server cannot erase the copy that matters.

  • Event: anything observable, and most events are harmless. Alert: an event a rule has flagged. Incident: harms or threatens confidentiality, integrity or availability, or violates policy, and it triggers the incident response plan.
  • Prioritize confirmed alerts by impact on business functions, sensitivity of the data affected, and how hard recovery will be, not by arrival order.
  • Correlation in a SIEM links related records across sources and time into one meaningful alert.

Example: for the same employee, a door badge is used at the office at 22:05 and a VPN login arrives from another country at 22:07. Each record looks minor alone. Correlated, they point to stolen credentials, and the alert is ranked high because the account can reach customer data. Normalization only prepares records for this step.

Check yourself

1. Taken alone, a failed VPN login, a password reset and a large file upload each look routine, but together they describe one account takeover. Which SIEM function BEST addresses this?

2. A monitoring system records a failed login, a firewall rule match and a service restart; one of them proves to be an attacker's successful privilege escalation. Which statement BEST distinguishes an event from an incident?

Facts checked 2026-11-15 · Sources: ISC2 CC Certification Exam Outline, NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization

ISC2 Certified in Cybersecurity (CC) cheat sheet: every key fact on one page →