Study guide

15.3 Emerging Technologies Risk (AI/LLM, Quantum, IoT/OT)

Certified in Risk and Information Systems Control CRISC

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Risk Foundations

1.1 About the CRISC Exam 1.2 Exam Day Strategy & Question Analysis

2 Chapter 2: Enterprise Governance & Organizational Strategy

2.1 Enterprise Governance of IT & Strategic Alignment 2.2 Organizational Structures, Roles & RACI Matrix 2.3 The Three Lines Model & Assurance Coordination 2.4 Legal, Regulatory & Contractual Compliance

3 Chapter 3: Risk Governance Frameworks & ERM

3.1 Enterprise Risk Management Frameworks 3.2 Risk Appetite, Tolerance & Capacity 3.3 IT Risk Strategy Alignment with Business Objectives

4 Chapter 4: Risk Culture, Ethics & Policy Architecture

4.1 Risk Culture, Tone at the Top & Accountability 4.2 Ethics, Integrity & ISACA Code of Professional Ethics 4.3 Risk Policy, Standards, Guidelines & Procedures Architecture

5 Chapter 5: Asset Management & Business Resilience Governance

5.1 Asset Identification, Valuation & Data Classification 5.2 Data Ownership, Custodianship & Governance Roles 5.3 Business Resilience Governance & Strategic Alignment 5.4 Data Privacy Governance & Global Mandates

6 Chapter 6: IT Risk Identification & Threat Modeling

6.1 Risk Identification Techniques 6.2 Threat Landscape Analysis, Threat Actors & Attack Vectors 6.3 Vulnerability Assessment & Exposure Analysis 6.4 Risk Scenario Development & Threat Modeling

7 Chapter 7: Risk Analysis Methodologies & Evaluation

7.1 Qualitative Risk Analysis & Risk Matrices 7.2 Quantitative Risk Analysis & FAIR Framework 7.3 Semi-Quantitative Analysis & Monte Carlo Simulation 7.4 Risk Evaluation, Ranking & Prioritization Criteria

8 Chapter 8: Risk Register, Aggregation & BIA Integration

8.1 Risk Register Architecture, Maintenance & Lifecycle 8.2 Risk Aggregation, Correlation & Interdependencies 8.3 Business Impact Analysis (BIA) Integration

9 Chapter 9: Risk Treatment Strategies & Cost-Benefit Analysis

9.1 Risk Response Options 9.2 Cost-Benefit Analysis & Return on Security Investment (ROSI) 9.3 Developing & Implementing Risk Action Plans 9.4 Managing Residual Risk & Secondary Risk

10 Chapter 10: Control Design, Selection & Assessment

10.1 Control Types & Categories 10.2 Control Design Principles & Defense-in-Depth 10.3 Testing Control Design & Operating Effectiveness 10.4 Remediation of Control Deficiencies & Exceptions

11 Chapter 11: Third-Party & Supply Chain Risk Management

11.1 Third-Party Risk Management Lifecycle & Due Diligence 11.2 Vendor Contracts, SLAs & Right-to-Audit Clauses 11.3 Supply Chain Risk Management & Software Bill of Materials (SBOM) 11.4 Cloud Service Provider Governance & Shared Responsibility

12 Chapter 12: Risk Monitoring, KRIs & Executive Reporting

12.1 Key Risk Indicators (KRIs), Thresholds & Triggers 12.2 Aligning KRIs with KPIs & Business Performance Metrics 12.3 Stakeholder Risk Reporting & Governance Communication 12.4 Continuous Risk Monitoring & Automated Telemetry

13 Chapter 13: Enterprise IT Architecture & Operations

13.1 Enterprise Architecture & IT Governance Alignment 13.2 Cloud Computing & Virtualization Architecture Risk 13.3 Systems Resilience, High Availability & Infrastructure Redundancy 13.4 Technology Roadmaps, IT Portfolio & Project Risk Governance

14 Chapter 14: Information Security Principles, IAM & SSDLC

14.1 Information Security Principles & The CIA Triad 14.2 Identity & Access Management (IAM), PAM & RBAC 14.3 Cryptography, Encryption & Key Management (KMS) 14.4 Secure Software Development Lifecycle (SSDLC) & DevSecOps

15 Chapter 15: Incident Response, Resilience & Emerging Tech Risk

15.1 Incident Response Lifecycle & Containment Strategies 15.2 Business Continuity & Disaster Recovery Planning and Testing 15.3 Emerging Technologies Risk (AI/LLM, Quantum, IoT/OT) 15.4 Risk Program Maturity Assessment & Continuous Improvement

15.3 Emerging Technologies Risk (AI/LLM, Quantum, IoT/OT)

Key Takeaways Explain This Topic AI

Generative AI and Large Language Models (LLMs) introduce distinct threat vectors including direct/indirect prompt injection, training data poisoning, PII/IP leakage, and ungrounded hallucinations.

The NIST AI Risk Management Framework (NIST AI RMF 1.0) establishes four core functions—GOVERN, MAP, MEASURE, and MANAGE—to evaluate and mitigate socio-technical AI risks across the system lifecycle.

Quantum computing threatens classical asymmetric cryptography (RSA, ECC) via Shor's algorithm, necessitating cryptographic agility and immediate transition to Post-Quantum Cryptography (PQC) standards (FIPS 203, 204, 205).

Adversaries are actively executing 'Harvest Now, Decrypt Later' (HNDL) attacks to capture high-value encrypted data today, intending to decrypt it once cryptanalytically relevant quantum computers (CRQC) emerge.

Operational Technology (OT) and SCADA environments prioritize safety and availability over confidentiality; IT/OT convergence and the erosion of Purdue Model air-gaps introduce critical cyber-physical disruption risks.

Last updated: August 2026

15.3 Emerging Technologies Risk (AI/LLM, Quantum, IoT/OT)

Technological innovation drives competitive advantage, operational efficiency, and transformative business capabilities. However, rapid technological adoption without rigorous risk governance creates profound vulnerabilities. According to the ISACA Risk IT Framework and the CRISC Body of Knowledge , risk practitioners must maintain forward-looking visibility into Emerging Technologies Risk , evaluating potential failure modes, adversarial threat vectors, and compliance implications before emerging solutions are deployed into production.

Today, enterprise risk management must confront three major technological frontiers: Artificial Intelligence & Large Language Models (AI/LLMs) , Quantum Computing & Cryptographic Obsolescence , and the cyber-physical convergence of Internet of Things (IoT) and Operational Technology (OT/SCADA) . +-----------------------------------------------------------------------------+

  • | EMERGING TECHNOLOGIES RISK LANDSCAPE |
  • | |
  • | +-------------------+ +-------------------+ +-----------------+ |
  • | | ARTIFICIAL | | QUANTUM | | IoT / OT / | |
  • | | INTELLIGENCE & | | COMPUTING & | | SCADA CYBER- | |
  • | | LLM GOVERNANCE | | CRYPTOGRAPHY | | PHYSICAL RISK | |
  • | +-------------------+ +-------------------+ +-----------------+ |
  • | - Prompt Injection - Shor's Algorithm - IT/OT Convergence |
  • | - Data Leakage / IP - Harvest Now, - Purdue Model |
  • | - Hallucination / Bias Decrypt Later Air-Gap Erosion |
  • | - NIST AI RMF 1.0 - Post-Quantum PQC - Safety vs Conf. |
  • +-----------------------------------------------------------------------------+
  • 1. Artificial Intelligence & Large Language Model (LLM) Risk Profile

The integration of Generative AI, Retrieval-Augmented Generation (RAG), and autonomous AI agent architectures into enterprise workflows introduces novel attack surfaces that traditional cybersecurity controls cannot fully mitigate. +-----------------------------------------------------------------------------+

  • | ENTERPRISE LLM & RAG THREAT SURFACE |
  • | |
  • | [UNTRUSTED INPUT] ---> [DIRECT PROMPT INJECTION] ---> +---------------+ |
  • | (Attacker prompt) (Jailbreaks, system override) | | |
  • | | ENTERPRISE | |
  • | [EXTERNAL DATA] ---> [INDIRECT PROMPT INJECTION]--> | LLM / AGENT | |
  • | (Web/PDF payload) (Hidden payload in context) | ENGINE | |
  • | | | |
  • | [POISONED CORPUS] ---> [DATA POISONING] ------------> +-------+-------+ |
  • | (Manipulated data) (Biased / backdoored weights) | |
  • | v |
  • | [UNGUARDED OUTPUT]<--- [DATA LEAKAGE / HALLUCINATION] <-------+ |
  • | (Exfiltrated PII, (Autonomous SQL execution, |
  • | fabricated facts) toxic output, PII leakage) |
  • +-----------------------------------------------------------------------------+

Primary LLM Vulnerability Classes (OWASP Top 10 for LLMs):

Direct Prompt Injection (Jailbreaking): An adversary crafts adversarial input prompts that trick the model into ignoring its system safety instructions, unlocking restricted functionality or confidential system directives.

Indirect Prompt Injection: An attacker places malicious instructions inside external data sources (e.g., a PDF resume, webpage, or supplier invoice). When an enterprise LLM ingests this document via a RAG pipeline, the embedded instructions execute within the LLM's context, potentially causing it to exfiltrate private internal data or trigger unauthorized downstream actions.

Training Data Poisoning: Malicious tampering with pre-training datasets or fine-tuning corpora, introducing intentional security backdoors, biased algorithmic outputs, or degraded performance.

Sensitive Data Leakage & Intellectual Property Loss: Employees inputting proprietary source code, trade secrets, or customer PII into public or third-party AI models, resulting in data exposure or inclusion in future model training runs.

Hallucination & Confabulation: The generation of statistically plausible but completely false factual claims, fake code libraries, or erroneous legal citations, creating significant operational, legal, and reputational liability.

Insecure Output Handling: Passing unvalidated LLM output directly to backend database interpreters (SQLi), web browsers (XSS), or system shells (Remote Code Execution) without sanitization.

2. AI Governance: NIST AI RMF & ISO/IEC 42001

To manage socio-technical AI risks, risk practitioners leverage structured frameworks such as the NIST AI Risk Management Framework (NIST AI RMF 1.0) and ISO/IEC 42001 ( Artificial Intelligence Management System ). +-----------------------------------------------------------------------------+

  • | NIST AI RMF 1.0 CORE FUNCTIONS |
  • | |
  • | +---------------------------------------------------------------------+ |
  • | | 1. GOVERN | |
  • | | - AI risk culture, policies, accountability, roles, workforce | |
  • | +----------------------------------+----------------------------------+ |
  • | | |
  • | +----------------------------+----------------------------+ |
  • | | | |
  • | v v |
  • | +--------------------------+ +--------------------------+ |
  • | | 2. MAP | | 3. MEASURE | |
  • | | - Context & capabilities | <-----------> | - Metrics, testing, | |
  • | | - Categorize impacts | | benchmarks, audits | |
  • | +-------------+------------+ +------------+-------------+ |
  • | | | |
  • | +--------------------+--------------------+ |
  • | | |
  • | v |
  • | +---------------------------------------------------------------------+ |
  • | | 4. MANAGE | |
  • | | - Prioritize & treat risks, deploy guardrails, continuous monitor | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Key Characteristics of Trustworthy AI (NIST AI RMF):

Valid & Reliable: The AI system performs accurately and consistently within its intended operating parameters.

Safe: The AI system does not endanger human life, health, property, or the environment.

Secure & Resilient: The AI system withstands adversarial manipulation, extraction, and degradation.

Accountable & Transparent: Decision logic is auditable, and human accountability is maintained.

Explainable & Interpretable: The outputs and underlying mechanisms can be understood and reasoned about by human operators.

Privacy-Enhanced: Personal data is safeguarded throughout training, fine-tuning, and inference.

Fair with Bias Managed: Algorithmic bias and discriminatory outcomes are systematically identified and mitigated.

Note

Human-in-the-Loop (HITL) Controls: For high-risk AI deployments (e.g., credit underwriting, automated loan denial, medical diagnostics, personnel recruitment), governance policies must mandate Human-in-the-Loop verification, ensuring automated algorithms cannot execute binding decisions without human oversight.

3. Quantum Computing & Cryptographic Resilience

Quantum computers leverage quantum mechanics (superposition, entanglement) to solve specific mathematical problems exponentially faster than classical supercomputers. This capability poses an existential threat to modern digital security. +-----------------------------------------------------------------------------+

  • | THE QUANTUM CRYPTOGRAPHIC THREAT MATRIX |
  • | |
  • | CRYPTOGRAPHIC FAMILY QUANTUM ALGORITHM QUANTUM IMPACT |
  • | ----------------------- ----------------- ----------------------- |
  • | Asymmetric (Public Key) Shor's Algorithm TOTAL BREAK |
  • | - RSA, ECC, Diffie- (Polynomial time - Compromises key |
  • | Hellman, DSA, ECDSA period finding) exchange, signatures, |
  • | and encryption |
  • | Symmetric Encryption Grover's Algorithm PARTIAL IMPACT (Halved) |
  • | - AES-128 (Quadratic speedup - AES-128 -> 64-bit (Weak)|
  • | - AES-256 search) - AES-256 -> 128-bit (Safe|
  • | Cryptographic Hashes Grover's Algorithm PARTIAL IMPACT (Halved) |
  • | - SHA-256, SHA-3 (Collision search) - SHA-256 -> 128-bit (Safe|
  • +-----------------------------------------------------------------------------+
  • The "Harvest Now, Decrypt Later" (HNDL) Threat

Adversaries (particularly nation-states) are currently intercepting and storing massive volumes of encrypted diplomatic cables, financial records, medical histories, and intellectual property. Although they cannot decrypt this traffic today, they intend to decrypt it once a Cryptanalytically Relevant Quantum Computer (CRQC) becomes operational (estimated between 2030-2035). If data confidentiality requirements exceed 10 to 20 years, the risk is imminent today .

NIST Post-Quantum Cryptography (PQC) Standards (August 2024):

To counteract the quantum threat, the U.S. National Institute of Standards and Technology (NIST) finalized the primary PQC standards:

FIPS 203 (ML-KEM): Module-Lattice-Based Key-Encapsulation Mechanism (derived from CRYSTALS-Kyber) for general public-key encryption and key exchange.

FIPS 204 (ML-DSA): Module-Lattice-Based Digital Signature Algorithm (derived from CRYSTALS-Dilithium) for general digital signatures.

FIPS 205 (SLH-DSA): Stateless Hash-Based Digital Signature Algorithm (derived from SPHINCS+) as a backup stateless signature standard.

Important

Cryptographic Agility: Enterprises must establish Cryptographic Agility —the architectural ability to dynamically inventory, replace, and upgrade cryptographic algorithms and certificates across hardware, software, and protocols without requiring extensive recoding or infrastructure redesign.

4. IoT, OT, and SCADA Cyber-Physical Systems

Operational Technology (OT) refers to hardware and software that detects or causes changes in physical processes (e.g., power grids, chemical plants, water treatment, manufacturing assembly lines). The convergence of enterprise IT networks with legacy OT systems creates acute cyber-physical security risks. +-----------------------------------------------------------------------------+

  • | THE PURDUE ENTERPRISE REFERENCE ARCHITECTURE |
  • | |
  • | ENTERPRISE [LEVEL 5: Enterprise Network / Cloud Telemetry] |
  • | IT DOMAIN [LEVEL 4: Business Logistics & ERP Systems] |
  • | ====================== [INDUSTRIAL DMZ / FIREWALL] =======================|
  • | OPERATIONAL [LEVEL 3: Site Operations, SCADA Servers, Historians] |
  • | TECHNOLOGY [LEVEL 2: Area Supervisory Control, HMIs] |
  • | (OT) DOMAIN [LEVEL 1: Basic Control - PLCs, RTUs, DCS Controllers] |
  • | [LEVEL 0: Physical Process - Valves, Pumps, Sensors, Actuators|
  • +-----------------------------------------------------------------------------+

Contrasting IT vs. OT Risk Priorities:

Attribute Information Technology (IT) Operational Technology (OT / ICS)

Core Objective Data confidentiality, processing integrity, and business throughput. Physical safety of human life, asset integrity, and continuous uptime.

Priority Triad Confidentiality > Integrity > Availability (CIA). Safety > Availability > Integrity > Confidentiality (AIC).

Asset Lifespan 3 to 5 years (Rapid refresh cycles). 15 to 30 years (Legacy systems, difficult to upgrade).

Patching Philosophy Regular, automated, weekly/monthly patch cycles. Infrequent, highly restricted maintenance windows; patching can void certifications.

Protocol Security Encrypted, authenticated protocols (TLS, SSH, Kerberos). Cleartext, unauthenticated industrial protocols (Modbus, DNP3, Profibus).

Protecting Converged OT Environments:

Industrial DMZ (IDMZ): Establishing a strict buffer zone between IT (Level 4) and OT (Level 3) with no direct routing, utilizing jump hosts and multi-factor authentication.

Unidirectional Data Diodes: Physical hardware devices that enforce one-way data transfer, allowing plant telemetry and historian replication to flow up to enterprise IT while physically preventing inbound attack traffic into OT controllers.

Passive Network Monitoring: Using passive network taps and packet inspection to detect anomalies without injecting active scanning packets that can crash sensitive legacy Programmable Logic Controllers (PLCs).

  • 5. CRISC Exam Traps & Real-World Scenarios
  • Exam Trap 1: Misunderstanding Quantum Symmetric Encryption Impact

The Trap: A candidate assumes quantum computing breaks AES-256 symmetric encryption just as it breaks RSA.

The Reality: Shor's algorithm completely breaks asymmetric public key cryptography (RSA, ECC). Grover's algorithm only provides a quadratic speedup against symmetric ciphers (effectively halving the key length). Therefore, AES-256 remains cryptographically secure against quantum attacks because it provides 128 bits of quantum security.

Exam Trap 2: Active Vulnerability Scanning in OT/SCADA Environments

The Trap: An IT security auditor suggests running an active vulnerability port scanner (e.g., Nessus, Nmap) across an industrial manufacturing network to find unpatched PLCs.

The Reality: Active network scanning can overwhelm legacy OT devices, causing PLCs to freeze, crash, or enter unsafe failure states, potentially triggering physical damage or endangering human workers. OT environments require passive network monitoring .

Exam Trap 3: Dismissing AI Hallucination as a Software Bug

The Trap: Treating LLM hallucinations as minor developer bugs that do not require enterprise risk management oversight.

The Reality: Hallucinations in automated customer advice, medical analysis, or financial reporting introduce severe operational, legal liability, and regulatory compliance risks that must be bounded by human-in-the-loop controls and output guardrails.