Study guide

Internal and External Influences

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

Internal and External Influences

Key Takeaways Explain This Topic AI

Internal drivers (culture, structure, risk appetite) and external drivers (laws, regulators, contracts, threat landscape) jointly shape the security strategy a CISM manager must defend.

A PESTLE/SWOT-style environmental scan is the governance tool the exam expects before strategy is set, not a tool purchase.

Legal and regulatory obligations (GDPR, HIPAA, PCI DSS, SOX) are hard constraints; the manager translates them into policy, not the other way around.

Information Security Governance is 18% of the ISACA outline in effect since 3 November 2026; the exam rewards the answer that aligns security direction with business objectives.

Last updated: November 2026

Internal and External Influences

Information security governance is the system of leadership, structure, and processes that directs and controls how an organization protects information. Before a strategy can be written, a security manager must scan the environment that shapes it. The ISACA Certified Information Security Manager (CISM) outline in effect since 3 November 2026 places governance at 18% of the exam (17% before that date), and this topic is the front door to that domain. The exam frames it as a question of inputs: what forces constrain or enable the program, and what is the manager's first move once a force is identified.

Internal influences come from inside the enterprise and are largely controllable over time. They include organizational culture, the reporting structure (does the Chief Information Security Officer report to the CIO, the CEO, or the board?), risk appetite and risk tolerance set by senior management, the maturity of existing processes, available budget and skills, and the firm's strategic plan.

External influences are imposed from outside and are usually non-negotiable: laws and regulations, contractual commitments to customers, industry standards, the threat and technology landscape, and stakeholder expectations such as those of regulators, auditors, and shareholders.

The governance tool the exam expects is an environmental scan , often expressed as PESTLE (Political, Economic, Social, Technological, Legal, Environmental) for external factors and SWOT (Strengths, Weaknesses, Opportunities, Threats) for the internal/external blend. A scan precedes strategy; a tool purchase or a control implementation does not. When a scenario describes a new privacy law, a merger, or a shift to cloud, the strongest CISM answer is to assess the impact on objectives and risk , then adjust direction — not to immediately deploy technology.

Translating constraints into direction

External legal and regulatory obligations are hard constraints : the General Data Protection Regulation (GDPR), the Health Insurance Portability and Accountability Act (HIPAA), the Payment Card Industry Data Security Standard (PCI DSS), and the Sarbanes-Oxley Act (SOX) define non-discretionary requirements. The manager's job is to translate them into policy and controls, never to weaken them for convenience. Internal forces, by contrast, are levers the manager helps shape over time.

  • Influence Type Manager's first governance move
  • New data-protection regulation External / legal Map obligations to current controls; report gaps to leadership
  • Board sets lower risk appetite Internal / cultural Re-baseline risk treatment and acceptance thresholds

Customer contract demands SOC 2 External / contractual Add the requirement to the control framework and audit scope

  • Ransomware surge in the sector External / threat Reassess incident readiness and resilience investment
  • CISO moved under the board Internal / structural Realign reporting lines and escalation authority

Two traps recur. First, candidates pick the most technical option (a firewall, an EDR tool) when the question asks what should happen first after an influence is identified — assessment and alignment come before procurement. Second, candidates treat internal preferences as overriding external law; a budget constraint never excuses non-compliance with a binding regulation.

Remember the exam baseline so you do not confuse logistics with content: CISM is 150 multiple-choice questions in 4 hours , scored 200-800 with 450 to pass , and the content outline in effect since 3 November 2026 weights governance at 18% — make sure your materials use that outline, not the 2022 one.

A reliable habit for this section: read the scenario, name whether the driver is internal or external, decide whether the manager should assess , align , escalate , or treat , and only then consider technology. That sequence is what separates a governance answer from a practitioner answer.

How influences flow into the program

Influences do not stop at strategy; they cascade into every governance artifact. A new external obligation becomes a policy change, then a standard, then a control, then a metric that proves compliance. An internal cultural shift — say, a board demanding faster digital delivery — changes risk appetite, which changes which risks are accepted versus treated, which changes the program roadmap. The CISM manager is the translator who keeps that chain coherent so the program never drifts from the forces acting on it.

Stakeholder analysis is part of reading influences. Each stakeholder group exerts a distinct pressure and expects a distinct form of communication, and the strongest exam answers respect those expectations:

The board and executives expect risk in business and financial terms, with clear accountability and decisions to make.

Regulators and auditors expect documented evidence that obligations are met and exceptions are managed.

Customers and partners expect contractual security commitments to be honored and demonstrable.

Business unit leaders expect security to enable, not block, their objectives.

Staff expect clear, usable policy and training rather than abstract rules.

When a question hinges on who is driving the requirement, identify the stakeholder, identify whether the force is internal or external, and pick the response that satisfies that stakeholder's legitimate expectation through governance — alignment, reporting, evidence, or treatment. A misread of the stakeholder is the most common reason a plausible-looking option is actually wrong. Internal and external influences, read correctly, are the compass for everything that follows in this domain: strategy, framework, integration, policy, and investment all answer to them.