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 3 of 4

Cloud characteristics and deployment models

1 min read

The CC outline uses the NIST SP 800-145 definition of cloud computing, which has five essential characteristics, three service models and four deployment models. Questions usually describe one detail and ask which characteristic it shows, so match the key word in the scenario.

CharacteristicClue in the scenario
On-demand self-serviceCapacity added through a portal with no human contact at the provider
Broad network accessReached over the network from laptops, tablets and phones
Resource poolingMany tenants share hosts, and capacity is reassigned by demand
Rapid elasticityCapacity grows and shrinks to match load
Measured serviceUse is metered and reported

The deployment models are public, private, community and hybrid. A private cloud is defined by exclusive use by one organization; a third party may own and run it, on or off the premises.

A community cloud is shared by several organizations with common concerns. A hybrid cloud binds two or more distinct models together, such as a dedicated environment for regulated records linked to a public platform for a marketing site.

Example: a hospital network hires a vendor to build a cloud on dedicated racks in the vendor's building, used by that hospital network alone. It is still a private cloud. If two other hospitals later join and share it for common compliance needs, it becomes a community cloud.

Check yourself

1. Virtual machines belonging to several unrelated customers run on the same physical hosts, and the provider reassigns capacity among them according to demand. Which essential characteristic is this?

2. A firm keeps its regulated records in an environment dedicated to itself, runs its public marketing site on a shared provider platform, and links the two. Which deployment model describes the result?

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 →