Study guide
Governance Frameworks and Standards
CISM Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISM Orientation and 2026 Exam Facts
Current CISM Exam Facts The November 2026 Outline Change The Security Manager Mindset Scaled Score and Preliminary Status Registration Scheduling and Fees Certification After Passing
2 Chapter 2: Information Security Governance
Organizational Culture and Governance Signals Legal, Regulatory, and Contractual Requirements Structures, Roles, and Responsibilities Information Security Strategy Development Governance Frameworks and Standards Strategic Planning, Budgets, and Business Cases
3 Chapter 3: Information Security Risk Management
Emerging Risk and Threat Landscape Vulnerability and Control Deficiency Analysis Risk Assessment and Analysis Risk Treatment and Response Options Risk and Control Ownership Risk Monitoring and Reporting
4 Chapter 4: Information Security Program Development
Program Resources: People, Tools, and Technologies Information Asset Identification and Classification Industry Standards and Frameworks Policies, Procedures, and Guidelines Information Security Program Metrics Program Alignment with Strategy
5 Chapter 5: Program Management and Control Execution
Security Control Design and Selection Control Implementation and Integration Control Testing and Evaluation Security Awareness and Training External Services and Supplier Management Program Communications and Reporting
6 Chapter 6: Incident Management Readiness
Incident Response Plan Business Impact Analysis Business Continuity Plan Disaster Recovery Plan Incident Classification and Categorization Incident Training Testing and Evaluation
7 Chapter 7: Incident Management Operations
Incident Management Tools and Techniques Incident Investigation and Evaluation Incident Containment Methods Incident Response Communications Incident Eradication and Recovery Post-Incident Review Practices
8 Chapter 8: Supporting Governance Tasks
Internal and External Influences Maintaining Security Strategy Governance Framework Maintenance Corporate Governance Integration Policy Direction and Standards Business Cases for Security Investment
9 Chapter 9: Cross-Domain Risk and Program Decisions
Senior Leadership Commitment Responsibilities and Lines of Authority Program Effectiveness Reporting Risk Process Oversight Threat and Vulnerability Participation Risk Appetite and Treatment Decisions
10 Chapter 10: External Parties Data and Emerging Technology
Information Security Requirements in Contracts Monitoring External Parties Information Asset Lifecycle Thinking Cloud SaaS and Provider Risk AI, Blockchain, and Ransomware Context Compliance and Control Evidence
11 Chapter 11: CISM Practice Strategy
Domain-Weighted Study Allocation Management-Focused Answer Choices One-Best-Answer Elimination Timed Four-Hour Practice Using Domain Feedback Correctly Retake, Rescore, and Post-Exam Feedback
12 Chapter 12: Final Review and Exam Day Readiness
Two-Week Final Review Plan Exam Day Rules and Identification Remote Proctoring Readiness Preliminary Status Versus Official Score Application Window, Experience, and Ethics CPE Maintenance After Certification
Governance Frameworks and Standards
Key Takeaways Explain This Topic AI
COBIT is a governance framework (it separates governance from management); ISO/IEC 27001 is a certifiable management-system standard; NIST CSF is a voluntary control framework.
Frameworks are adopted and tailored to the enterprise — never adopted wholesale without mapping to actual business risk and obligations.
ISO/IEC 27001 requires a defined ISMS scope, risk treatment, and management commitment; certification is to 27001, while 27002 is guidance on controls.
Policies set mandatory intent; standards make them measurable; procedures give step-by-step instructions; guidelines are optional recommendations.
Last updated: June 2026
Choosing Among the Major Frameworks
CISM expects you to know what each major framework is for and not to confuse them. The recurring trap is treating them as interchangeable.
Framework Type Best for Key distinction
COBIT (ISACA) Enterprise governance of IT Aligning IT/security with enterprise goals Explicitly separates governance from management objectives
ISO/IEC 27001 Certifiable management-system standard A formal, auditable ISMS You certify against 27001; 27002 is its control guidance
NIST Cybersecurity Framework (CSF) Voluntary control/outcome framework Risk-based control organization Functions: Govern, Identify, Protect, Detect, Respond, Recover
NIST SP 800-53 Control catalog US federal / detailed control baselines Prescriptive control set, not a management system
COBIT is the one CISM most closely aligns with for governance because it institutionalizes the governance-versus-management split discussed earlier. ISO/IEC 27001 matters when a question mentions certification , an Information Security Management System (ISMS) , or auditable scope. The NIST CSF (which added the Govern function in version 2.0) is the voluntary, outcome-based option often chosen by US private-sector enterprises.
Adopt and Tailor — Never Wholesale
The management lesson the exam rewards: a framework is selected and tailored to the enterprise's risk profile, obligations, size, and culture — not adopted line-for-line. Implementing every control in a catalog without mapping to actual risk wastes resources and creates controls nobody owns. The correct sequence is understand business risk and obligations, then select the framework that best fits, then tailor the controls to that context. A common wrong answer is "implement all controls in the standard."
ISO/IEC 27001 Essentials
When a stem invokes 27001, recall its mandatory pillars: a clearly defined ISMS scope , demonstrable top-management commitment , a risk assessment and risk treatment process, a Statement of Applicability justifying included/excluded controls, and continual improvement (often expressed as Plan-Do-Check-Act). Certification is granted against 27001 ; 27002 is non-certifiable guidance describing how the controls work. Mixing those two is a frequent distractor.
The Document Hierarchy
CISM tests precise definitions of governance documents because answer choices deliberately swap them:
Policy — high-level, mandatory statement of management intent and direction. Approved by senior management. Rarely changes. Answers "what and why."
Standard — mandatory, specific, measurable requirement that makes a policy enforceable (e.g., "passwords are at least 14 characters"). Answers "how much / to what level."
- Procedure — mandatory step-by-step instructions to accomplish a task. Answers "how, step by step."
- Guideline — optional , recommended best practice. Answers "suggested how."
The most common trap: calling a measurable, mandatory rule a "guideline." If it is mandatory and specific, it is a standard , not a guideline. Policies express intent; standards make that intent auditable; procedures operationalize it; guidelines merely advise. Keeping this hierarchy straight earns reliable points across Domain 1.
Frameworks for Risk, Privacy, and Assurance
Beyond the headline three, CISM expects recognition of frameworks aimed at specific governance needs, and the trap is matching the wrong tool to the need:
- Need Framework Note
- Enterprise risk management ISO 31000 / COSO ERM Risk principles and process, not security-specific
- Privacy management ISO/IEC 27701 Extends an ISO 27001 ISMS to a privacy information management system
Service-provider assurance SOC 2 (AICPA) Reports on controls for security, availability, confidentiality, etc.
- IT service management ITIL Operational processes, not a security framework
- US federal authorization NIST RMF / FedRAMP Authorizes systems against SP 800-53 baselines
A common distractor pairs a service-management framework like ITIL with a governance question, or treats SOC 2 as a certification the enterprise earns rather than an attestation a provider obtains for its customers. Knowing each framework's purpose — governance, management, risk, privacy, or assurance — is the discrimination the exam rewards.
Remember too the difference between a SOC 2 Type I report (controls suitably designed at a point in time) and a Type II report (controls operated effectively over a period, usually 6–12 months); when assessing a vendor's actual security posture, the Type II report is the stronger evidence because it demonstrates operating effectiveness, not just design.
Selecting and Integrating, Not Stacking
Mature programs frequently use more than one framework together — for example, COBIT for governance alignment, ISO/IEC 27001 for the management system, and NIST CSF to communicate risk-based outcomes — but they map and integrate them so controls are not duplicated or contradictory. A crosswalk (mapping one framework's controls to another's) prevents the team from operating two overlapping control sets. When a stem describes an enterprise that has adopted several frameworks and is drowning in redundant controls, the governance answer is to rationalize and map them to a single control set, not to drop one arbitrarily.
The closing discipline for this section: choose frameworks for what they govern, manage, or assure ; tailor controls to real risk and obligations rather than implementing catalogs wholesale; and keep the policy-standard-procedure-guideline hierarchy precise, since mislabeling a mandatory measurable rule as a guideline is the single most common document-type trap in Domain 1.