Study guide

Risk Identification in Business Context

ISC2 Certified in Cybersecurity CC

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Official 2026 CC Exam Facts and Timeline CAT Format and Beginner Security Judgment Domain Map and Time Allocation 30, 60, and 90 Day Study Plan with Readiness Thresholds

2 Domain 1: Security Principles (24%)

CIA Triad as a Practical Decision Tool Authentication, Authorization, Accounting, and Non-Repudiation Privacy in the CC Outline Beginner Security Decision Scenarios AI Security in Security Principles

3 Domain 1: Risk Management and Security Controls

Risk Identification in Business Context Risk Management Processes Risk Treatment Decisions Security Controls: Technical, Administrative, and Physical

4 Domain 1: Governance, Ethics, Policy, and Privacy

Governance and the ISC2 Code of Ethics Policies, Procedures, Standards, Laws, and Regulations Privacy and AI Governance Due Care, Due Diligence, and Governance Decisions

5 Domain 1: Physical Security Controls

Physical Controls and Their Monitoring Tailgating and Physical Penetration Testing

6 Domain 2: Security Governance - Business Continuity

Business Continuity (BC)

7 Domain 2: Security Governance - Disaster Recovery

Disaster Recovery (DR) Redundancy in Business Continuity and Disaster Recovery

8 Domain 2: GRC Planning

GRC Planning: Purpose, Importance, and Tools

9 Domain 2: Measuring Cybersecurity Effectiveness

Security Metrics, KRIs, and Dashboards AI Security in Governance, Awareness, and Continuity

10 Domain 2 and Domain 5: Security Awareness and Triage

Security Awareness and Organizational Culture Phishing and Password Protection Security Event Triage and Human Review

11 Domain 3: Identity Lifecycle Management

Identification, Authentication, Authorization, and Accountability Multi-Factor Authentication and Password Protection Provisioning, Deprovisioning, and Access Reviews Service Accounts and AI Bots in Identity Management AI Bots and Service Accounts in Identity Management

12 Domain 3: Logical Access Controls

Least Privilege and Separation of Duties DAC, MAC, RBAC, and ABAC

13 Domain 4: Networking Fundamentals

Network Models and IP Addressing Firewalls: Ports and Applications Virtual Private Networks (VPN) Wireless Networks and Embedded Systems

14 Domain 4: Network Security Architecture and Cloud Security

Network Segmentation Defense in Depth and Zero Trust Cloud Characteristics and Shared Security Model Cloud Service Models, Deployment Models, and Shared Security AI in Network Security and Cloud Hosting

15 Domain 5: Incident Response

Incident Response (IR) and the Incident Response Plan Preparing the Incident Response Plan Incident Response Exercises and Tabletops AI in Security Operations and Incident Response

16 Domain 5: Security Monitoring

Logging and Monitoring Security Events

17 Domain 5: Threat Actors and Threat Intelligence

Threat Actors, Threat Intelligence, and Frameworks

18 Domain 5: Data Security

Encryption and Hashing for Data Security Data Handling: Classification, Labeling, Masking, and Sanitization Security of the AI Workspace

19 Domain 5: Asset Protection

Configuration and Change Management Change Management and Asset Protection Asset Lifecycle and End-of-Life Management

20 Domain 5: Data Handling Policy

Data Handling Policy and Classification

21 Domain 5: Security Testing

Security Readiness, Application, and Physical Testing

22 Integrated CC Scenario Labs

Risk and Control Selection Drill Continuity, Recovery, and Response Drill Access Control Design Drill Segmentation and Triage Drill

23 Final 14-Day Review and Exam Readiness

CAT Pacing and 100-125 Item Strategy Missed-Question Notebook and Domain Repair Exam Day Logistics and Rescheduling After Passing: AMF and CPE

Risk Identification in Business Context

Key Takeaways Explain This Topic AI

Risk identification names the asset, threat, vulnerability, likelihood, and business impact before any control is chosen.

A strong risk statement links a specific weakness to a credible event and a measurable business consequence.

Assets include data, systems, facilities, people, suppliers, processes, and reputation, not just servers.

The ISC2 CC exam is 100-125 items, 2 hours, CAT delivery, passing score 700 of 1000, with Domain 1 weighted 24%.

Confusing a control with a risk and weighting every danger equally are the two most common CC scenario traps.

Last updated: October 2026

Key Concepts

In the ISC2 (International Information System Security Certification Consortium) Certified in Cybersecurity (CC) credential, Domain 1, Security Principles , carries the heaviest weight at 24% . The five domains weigh 24%, 21.3% (Networking and Cloud Security), 20% (Identity and Access Management), 17.3% (Security Operations and Incident Response), and 17.3% (Security Governance). The exam is 2 hours (120 minutes) with 100-125 items , delivered as computerized adaptive testing (CAT) in person at Pearson testing centers, scored on a scaled 700 of 1000 to pass. Do not convert 700 into a percentage; it is a scaled cut score, not a raw correct count.

The outline effective September 1, 2026 folds AI-security awareness into all five domains.

Risk is the possibility that a threat exploits a vulnerability to cause an adverse impact . Risk identification is the first practical step: deciding what needs protecting and why. It is not about predicting the future precisely; it is about producing a clear, defensible list of what could go wrong and what it would cost the business.

Start with assets . An asset is anything of value: a customer database, a laptop, a cloud account, a backup, a supplier relationship, an employee, a building, a business process such as payroll accuracy or patient scheduling, or intangible value such as public trust. New analysts fixate on servers and miss business assets. In scenario questions, ask what the organization depends on to operate, earn revenue, or stay compliant.

  • Element Question it answers Worked example
  • Asset What has value? Customer identity and payment records
  • Threat What could cause harm? Criminal phishing campaign targeting staff
  • Vulnerability What weakness exists? No multi-factor authentication (MFA) on remote email
  • Likelihood How plausible is it? High; phishing attempts are already being reported
  • Impact What business result follows? Account takeover, fraud, breach-notification cost

A useful risk statement connects these in plain language: "Because remote email lacks MFA, a stolen password could allow account takeover, leading to wire fraud, data exposure, and incident-response cost." That is far stronger than "phishing is a risk," because it names the weakness, the event, and the consequence the business actually cares about.

Exam Application

Identification draws on many evidence sources. Common ones include:

  • Asset inventories and data-flow diagrams
  • Vulnerability scans and penetration-test findings
  • Audit findings and compliance gap reviews
  • Incident and help-desk ticket history
  • Vendor and third-party security questionnaires
  • Threat intelligence and architecture interviews

Good identification draws evidence from several of these sources, not a single scan.

Business context changes priority. The same technical flaw on a lab box, a public marketing page, and a payroll server produces very different impact. A warehouse-camera outage is minor in one firm and critical in another if cameras feed a regulated chain-of-custody evidence process. Always read identification through the lens of data sensitivity, exposure, the dependent business process, and recovery difficulty.

Work a scenario: a small clinic stores patient data on one shared workstation with a single local login. The asset is patient information plus clinical availability. Threats include unauthorized access, malware, theft, and accidental change. Vulnerabilities include the shared credential, weak access control, no logging, and possibly missing encryption. Impacts include privacy violation, care delay, regulatory exposure, and lost trust.

Avoid the two common traps. First, do not confuse a control with a risk. "Install MFA" is a treatment; the risk is account takeover from weak authentication. Second, do not weight every danger equally — a risk list that ignores asset value and likelihood becomes noise. When a question asks for the best next step early in risk work, the answer usually means identify assets, document threats and vulnerabilities, engage the business owner, and clarify impact before buying expensive controls. Read each scenario for the asset, the weakness, and the consequence.

Vocabulary to keep straight. A threat is the potential cause of harm; a threat actor (or threat agent) is the person or thing that carries it out, such as a criminal group, an insider, or a natural event like a flood. A vulnerability is the weakness the threat can use. An exploit is the specific technique or tool that takes advantage of a vulnerability. A risk is the combination — the chance that a threat exploits a vulnerability to harm an asset. Answer choices often mix these terms: when a question asks you to name the threat , an answer describing the weakness is wrong, and vice versa.

It also helps to separate threat sources so you can reason about likelihood. A mature identification effort considers more than hackers. A scenario about a single hard drive with no backup describes an availability loss, not necessarily an attacker. Always let the scenario's facts — who or what acts, against which asset, through which weakness — drive the identification rather than assuming every event is a deliberate attack.

Source: ISC2 CC Exam Outline effective September 1, 2026 (v01/2026), subdomain 1.2 (risk management lifecycle and processes), checked 2026-10-22.