Certified Chief Information Security Officer v4 (CCISO) — Lesson 2: Risk Management, Compliance, Assurance, and Control Architecture

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Risk Appetite and Enterprise Risk.
• Implement and validate Regulatory Mapping, Control Design, and Assurance Planning and Third-Party Oversight using reviewable evidence.
• Evaluate the condition where a control passes a basic check but fails during Control Design because Regulatory Mapping data, version, or dependency assumptions differ and select a proportionate corrective response.

Detailed Topics

• Risk Appetite applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Enterprise Risk applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Regulatory Mapping applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Control Design applied to the course scenario, expected behavior, dependencies, controls, and evidence.
• Assurance Planning and Third-Party Oversight applied to the course scenario, expected behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an enterprise security leader must align cyber risk with business priorities, investment decisions, regulatory duties, and measurable resilience. The walkthrough connects tools, configuration or analysis logic, system messages, decisions, and evidence captured in the enterprise security operating model, risk-appetite statement, investment portfolio, and board-assurance pack. It also tests the exception where a control passes a basic check but fails during Control Design because Regulatory Mapping data, version, or dependency assumptions differ.

Hands-On Exercise

Complete a controlled, authorized EC-Council exercise covering Risk Management, Compliance, Assurance, and Control Architecture and preserve the verified result in the enterprise security operating model, risk-appetite statement, investment portfolio, and board-assurance pack.

1. Confirm scope, authorization, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, outputs, events, decisions, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception without targeting real third-party systems.
4. Document corrections, evidence, ownership, retest criteria, rollback or recovery, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences Risk Appetite.
• Compare two defensible responses and explain technical, security, operational, legal, and support trade-offs.
• Determine how the enterprise security operating model, risk-appetite statement, investment portfolio, and board-assurance pack should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check authorization, prerequisites, identity, configuration order, data quality, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “a control passes a basic check but fails during Control Design because Regulatory Mapping data, version, or dependency assumptions differ” as a hypothesis until logs, settings, captured outputs, and retest outcomes confirm the cause.

Validation Checklist

• Required components, identities, permissions, settings, safety controls, and dependencies are present.
• The enterprise security operating model, risk-appetite statement, investment portfolio, and board-assurance pack connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback or recovery, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Risk Management, Compliance, Assurance, and Control Architecture, explain the resulting security or operational behavior, and defend the outcome through the enterprise security operating model, risk-appetite statement, investment portfolio, and board-assurance pack.