Study guide

Legal, Regulatory, and Contractual Requirements

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

Legal, Regulatory, and Contractual Requirements

Key Takeaways Explain This Topic AI

Compliance is a constraint and a driver of the strategy, but CISM treats it as a floor — meeting the law is not the same as managing risk.

The manager maintains a legal/regulatory register and maps each obligation to owned, monitored controls with evidence.

Contracts (SLAs, DPAs, right-to-audit clauses) impose security obligations that are enforced like regulation and flow down to subcontractors.

Jurisdiction matters: GDPR breach notice is 72 hours; conflicting laws are resolved by senior management with legal counsel, not by the security team alone.

Last updated: June 2026

Compliance Is a Floor, Not a Strategy

CISM treats legal, regulatory, and contractual requirements as mandatory inputs that constrain the security strategy. They define a minimum baseline — the floor. A frequent exam trap offers "achieve compliance" as the program's goal; the manager answer is that compliance is necessary but insufficient, because a compliant enterprise can still hold unacceptable residual risk. The strategy must satisfy the law and manage risk to within appetite.

The manager's instrument is a legal and regulatory requirements register that ties each obligation to an owner, the controls that satisfy it, and the evidence proving it. Without that mapping, an audit finding ("we cannot demonstrate the control") is as damaging as the absence of the control itself.

Inventory, Map, Monitor

The disciplined sequence the exam rewards is identify obligations, map them to controls, then monitor for change :

Identify every applicable law, regulation, standard, and contractual clause across all jurisdictions where the enterprise operates or holds data.

Map each obligation to a specific control and a named accountable owner.

Maintain evidence (logs, attestations, test results) that demonstrates each control operates.

Monitor the legal landscape for changes and re-assess when laws or contracts change.

  • Obligation type Example Security implication
  • Privacy regulation GDPR (EU) 72-hour breach notification; lawful basis; data subject rights
  • Sector regulation HIPAA (US healthcare) Safeguards for protected health information; breach reporting
  • Card industry contract PCI DSS Cardholder-data controls enforced via merchant agreement
  • Right-to-audit clause Vendor MSA Customer can inspect the provider's controls on demand
  • Data processing agreement DPA Defines processor duties, sub-processor flow-down, breach notice
  • Contracts Behave Like Regulation

Contractual security obligations — service level agreements (SLAs) , data processing agreements (DPAs) , and right-to-audit clauses — are enforceable commitments and are tested with the same seriousness as statutory rules. Critically, obligations flow down to subcontractors: if a DPA prohibits storing data outside a region, the enterprise must contractually bind every sub-processor to the same term and verify it. Accepting a customer's right-to-audit clause without the capacity to honor it is a governance failure the manager must flag before signing.

Jurisdiction and Conflicting Laws

When the enterprise spans jurisdictions, obligations can conflict — for example, a law mandating data retention versus a privacy law mandating erasure. CISM's position is that the security manager does not resolve legal conflicts unilaterally . The correct action is to escalate to senior management and legal counsel , document the decision and its rationale, and implement the agreed treatment. The manager's role is to surface the conflict, quantify the risk, and execute the governed decision — not to choose which law to break.

Apply the stricter standard as a default working assumption pending legal guidance, because over-protecting data rarely creates legal liability while under-protecting it does.

Data Residency, Cross-Border Transfer, and Notification Clocks

Many Domain 1 questions hinge on specific obligations attached to where data lives and moves . Data residency rules require certain data to stay within a jurisdiction; cross-border transfer restrictions (such as the EU's mechanisms for moving personal data outside the bloc) require a lawful transfer basis. The security manager translates these into architecture and contract requirements — region-locked storage, transfer agreements, sub-processor controls — and verifies them, because a vendor's casual replication to another region can silently violate a binding term.

Notification timelines are favorite exam facts because they are precise and testable. Commit the headline numbers and treat them as floors set by the obligation, not as the manager's discretion:

  • Obligation Trigger Required action / clock
  • GDPR Personal-data breach with risk to individuals Notify supervisory authority within 72 hours

HIPAA Breach Notification Breach of unsecured protected health information Notify individuals without unreasonable delay, no later than 60 days

  • PCI DSS Suspected cardholder-data compromise Notify acquirer/brands per contract, typically immediately
  • Contractual DPA Breach affecting processed data Notify controller within the agreed window (often 24–72 hours)
  • Compliance Drives, but Risk Decides

A subtle but heavily tested distinction: regulation can be a driver that justifies funding ("this initiative is required for HIPAA"), yet the program is still organized around risk , not around a checklist. The trap answer treats the regulation as the entire scope; the manager answer treats it as one mandatory input among several. When a regulation and a risk assessment point to different priorities, the manager funds the legally mandatory item and documents any residual risk the regulation does not address, presenting it to management for an acceptance decision.

Note also that liability is not erased by outsourcing: when a third party processes regulated data, the originating enterprise generally remains accountable to regulators and customers even though the processor is responsible for execution. A frequent trap presents "the cloud provider is certified, so we are covered" — the manager answer is that certification reduces but does not transfer accountability, and the enterprise must still validate the provider's controls through the contract, attestations, and right-to-audit rights.

The closing discipline for this section: maintain the register, map every obligation to an owned and evidenced control, monitor for legal change, escalate conflicts, and never mistake the compliance floor for the risk ceiling — the exact reasoning Domain 1 rewards on legal and contractual stems.