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 →
← Network Architecture & Cloud Security

Chapter 8 · Lesson 4 of 4

Service models and the shared security model

1 min read

The three service models differ in how much of the stack the customer still manages. In Infrastructure as a Service (IaaS) the customer runs the operating system and everything above it. In Platform as a Service (PaaS) the provider also handles the operating system and runtime, and the customer deploys and configures its own application.

In Software as a Service (SaaS) the provider runs the application too. So moving from IaaS to PaaS to SaaS, the customer's share shrinks at each step.

  • Always the customer's: its data, the identities it creates and the rights it grants, and the configuration choices it makes, even in SaaS.
  • Always the provider's: the physical facility, the hardware, and the virtualization layer that separates tenants.

Example: a bakery chain uses a hosted email service and an employee shares a folder with a public link. The provider kept its data center secure, but the exposure came from a sharing setting the bakery controls.

A company can delegate security tasks to a provider, but not accountability for its data; the contract and service level agreement define duties and audit rights.

Check yourself

1. Under IaaS, PaaS and SaaS alike, which responsibilities stay with the customer in every case?

2. An executive says that once workloads move to a provider, any breach of the company's customer data becomes entirely the provider's problem. Which principle corrects that view?

Facts checked 2026-11-15 · Sources: ISC2 CC Certification Exam Outline, NIST SP 800-145, The NIST Definition of Cloud Computing

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