SCLE Module 17 study materials
SCLE Module 17 study resources

SCLE Module 17 study plan

SCLE Module 17 · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Governance, Risk, and Compliance & Foundational Concepts and Terminology

  • Define the core vocabulary of the exam (control, risk, threat, vulnerability, asset, likelihood, impact, residual risk) in your own words and match each term to a scenario

  • Map the governance layer: policy, standard, procedure, guideline, and baseline, and state who typically approves each

  • Build a risk register with eight realistic entries, scoring each on likelihood and impact and justifying the score

  • Classify five controls by type (preventive, detective, corrective, compensating) and by category (technical, administrative, physical)

Your checkpoint

A one-page terminology glossary plus an eight-row risk register with written scoring rationale

Week 2

Governance, Risk, and Compliance & Foundational Concepts and Terminology

  • Walk through a full risk assessment cycle from asset identification to treatment decision, and document the accept/mitigate/transfer/avoid choice for each register entry

  • Distinguish the obligations created by common regulatory and standards frameworks at a conceptual level, and list what evidence each typically demands

  • Draft a control-to-framework mapping table showing where one control satisfies multiple requirements

  • Identify three situations that create a conflict of interest or an independence problem in a compliance role and state the correct response

Your checkpoint

A completed risk treatment plan covering all eight register entries, each with owner, decision, and target date

Week 3

Architecture, Design, and Implementation & Foundational Concepts and Terminology

  • Diagram a reference architecture with trust boundaries marked, and annotate where authentication, authorization, and logging occur

  • Explain defense in depth and least privilege using your own diagram, and identify two places where the design violates least privilege

  • Compare three data protection approaches (encryption at rest, tokenization, masking) and select one for each of four data flows with justification

  • Describe how identity, credential, and session management decisions affect the rest of the architecture

Your checkpoint

A one-page architecture diagram with trust boundaries and a written list of five design weaknesses with proposed fixes

Week 4

Architecture, Design, and Implementation & Operations and Incident Response

  • Translate the architecture from week 3 into an implementation checklist of at least fifteen configuration items

  • Write secure configuration requirements for logging, access control, and change management that a builder could act on

  • Draft a change management workflow with approval gates and rollback criteria

  • Prepare a pre-deployment review checklist that catches the five most common design-to-implementation gaps

Your checkpoint

An implementation and secure configuration checklist of at least fifteen items, each with a pass/fail test

Week 5

Operations and Incident Response & Governance, Risk, and Compliance

  • Build an incident response plan covering preparation, detection, containment, eradication, recovery, and lessons learned, with named roles for each phase

  • Write three tabletop injects based on your week 3 architecture and record the decisions each inject forces

  • Define escalation thresholds and notification obligations, including who must be told and within what timeframe

  • Connect incident evidence handling to the compliance and legal obligations identified in week 2

Your checkpoint

A written incident response plan with a completed tabletop exercise summary and a decision log

Week 6

Monitoring, Testing, and Assurance & Operations and Incident Response

  • Design a monitoring plan that names the specific events to log, the alert thresholds, and the owner for each alert

  • Select assurance activities (vulnerability assessment, penetration test, configuration audit, control self-assessment) for four scenarios and justify each choice

  • Write five test procedures that produce pass/fail evidence rather than opinion

  • Explain how monitoring findings feed back into incident response and risk treatment

Your checkpoint

A monitoring and assurance plan with five testable procedures and defined evidence artifacts for each

Week 7

Monitoring, Testing, and Assurance & Professional Practice and Ethics

  • Interpret a sample set of audit findings and write a management response for each, including remediation owner and date

  • Distinguish assurance, audit, and assessment, and state when each is appropriate

  • Apply the professional practice obligations of due care, confidentiality, objectivity, and scope discipline to four short ethical scenarios

  • Identify the correct action when asked to sign off on evidence you did not personally verify

Your checkpoint

Four written ethical and professional judgment responses plus a sample management response to three audit findings

Week 8

Foundational Concepts and Terminology & Governance, Risk, and Compliance & Architecture, Design, and Implementation & Operations and Incident Response & Monitoring, Testing, and Assurance & Professional Practice and Ethics

  • Synthesize all prior deliverables into a single cross-referenced study summary organized by domain

  • Re-derive the weakest ten concepts from memory and correct them against your notes

  • Complete two timed mixed-domain practice sets and categorize every miss by domain and by cause (knowledge gap, misread, or guess)

  • Write a one-page exam-day strategy covering pacing, question triage, and how you will handle unfamiliar terminology

Your checkpoint

A categorized error log from two timed practice sets with a remediation note for every miss

Milestones

Week 2: You can explain the full risk assessment cycle and produce a defensible treatment decision for any register entry without notes

Week 4: Your architecture diagram and implementation checklist align item for item, with no design element lacking a configuration requirement

Week 6: You can trace any monitoring alert through to an incident response action and back to a risk it reduces

Week 8: Practice-set accuracy is at or above 75% overall, with no domain below 60% and every miss logged with a cause