Study guide

6.3 Clause 6: Planning

PECB ISO/IEC 27001:2022 Foundation Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts

2 Information Security Fundamentals

2.1 The CIA Triad 2.2 Beyond CIA: Authenticity, Non-repudiation, Accountability, Reliability 2.3 PECB ISMS Terminology 2.4 Information Security Roles and Responsibilities 2.5 Artificial Intelligence and Cloud Computing Characteristics

3 The ISO/IEC 27000 Family of Standards

3.1 The ISO/IEC 27000 Family 3.2 ISO/IEC 27001 vs ISO/IEC 27002 — The Classic Exam Trap

4 Information Security Risk Management

4.1 The Risk Management Process 4.2 The Four Risk Treatment Options 4.3 Risk Treatment Plan, Risk Owners, and the Path to Controls

5 ISMS Foundations

5.1 ISMS Purpose, Scope, and Benefits 5.2 The PDCA Cycle Applied to the ISMS

6 ISO/IEC 27001:2022 Clauses 4-6 (Context, Leadership, Planning)

6.1 Clause 4: Context of the Organization 6.2 Clause 5: Leadership 6.3 Clause 6: Planning

7 ISO/IEC 27001:2022 Clauses 7-10 (Support, Operation, Evaluation, Improvement)

6.4 Clause 7: Support 6.5 Clause 8: Operation 6.6 Clause 9: Performance Evaluation 6.7 Clause 10: Improvement

8 Annex A Controls and the Statement of Applicability

7.1 Annex A Structure: 93 Controls in 4 Themes 7.2 Annex A Organizational (37) and People (8) Controls 7.3 Annex A Physical (14) and Technological (34) Controls 7.4 The Statement of Applicability (SoA)

9 Certification and Continual Improvement

8.1 The ISMS Certification Process 8.2 Continual Improvement, Maintenance, and the Foundation vs Lead Track

6.3 Clause 6: Planning

Key Takeaways Explain This Topic AI

Clause 6 turns leadership intent (Clause 5) into a concrete plan: it addresses risks/opportunities and sets objectives

6.1.2 requires a formal information security risk assessment process with defined criteria (impact, likelihood, acceptance) — this is the bridge to the dedicated risk-management chapter

6.1.3 requires a risk treatment process that produces a Statement of Applicability (SoA) — explicitly required at 6.1.3 d) — and a risk treatment plan

6.2 requires information security objectives to be SMART: specific, measurable, monitored, communicated, and updated, and consistent with the policy

The SoA must include justification for control inclusion/exclusion and the status of implementation — a high-yield exam topic

Last updated: July 2026

Clause 6 is where the ISMS becomes a plan. After Clause 4 establishes context and Clause 5 commits leadership, Clause 6 requires the organization to plan actions that address risks and opportunities (6.1) and to set measurable information security objectives (6.2). This is the Plan stage of PDCA in its purest form, and it is the bridge from the main clauses to the risk-management chapter you have already studied.

  • 6.1 Actions to Address Risks and Opportunities
  • 6.1.1 General

When planning for the ISMS, the organization must consider the issues (4.1) and requirements (4.2) referred to above, and determine the risks and opportunities that need to be addressed to:

  • Give assurance that the ISMS can achieve its intended outcomes
  • Prevent, or reduce, undesired effects
  • Achieve continual improvement

The organization must then plan actions to address those risks and opportunities, including how to integrate and implement them into the ISMS processes and how to evaluate the effectiveness of those actions.

Risk vs. Opportunity

  • Concept What it Addresses Example
  • Risk Undesired effects on information security Data breach, regulatory fine, system outage

Opportunity Favorable effects that can be exploited New secure-by-design product line, automation that reduces human error

Both must be addressed — the exam sometimes assumes Clause 6.1 is only about risk; that is a trap.

6.1.2 Information Security Risk Assessment

The organization must define and apply an information security risk assessment process that:

Establishes and applies information security risk criteria including: risk acceptance criteria, criteria for performing risk assessments, and criteria for the evaluation of risks

  • Ensures that consistent, valid, and comparable risk assessment results are produced
  • Ensures the risk assessment identifies risks , analyses them, and evaluates them
  • Keeps the risk assessment results as documented information
  • The Three Phases of Risk Assessment

Phase What Happens

Identification Identify risks associated with the loss of confidentiality, integrity, and availability of information, asset owners, threat sources, vulnerabilities, and impacts

Analysis Estimate consequences (impact) and likelihood; combine to produce a risk level

Evaluation Compare the risk level against risk acceptance criteria to decide whether the risk is acceptable or needs treatment

Risk Acceptance Criteria

Risk acceptance criteria define the threshold above which a risk must be treated. They are set before the assessment is performed, often by top management or a risk owner, and they must be documented. A common trap is to claim criteria are set after the assessment so they can be tuned to the results — that defeats the purpose and is not allowed.

Connection to the Risk-Management Chapter

Clause 6.1.2 is the authoritative hook for everything in the dedicated risk-management chapter: threat catalogs, vulnerability identification, impact/likelihood scoring, risk registers, and the difference between qualitative and quantitative methods. The Foundation exam assumes you understand that 6.1.2 is the standard-side anchor of those techniques.

6.1.3 Information Security Risk Treatment

Once the risk assessment identifies risks that need treatment, the organization must implement a risk treatment process that:

Selects appropriate risk treatment options — the four classic options are:

  • Avoid — eliminate the risk by changing the activity
  • Modify (reduce/mitigate) — apply controls to lower likelihood or impact

Share (transfer) — outsource or insure (note: insurance does not transfer the underlying information risk, only the financial impact)

Retain (accept) — consciously accept the risk after analysis

Determines all necessary controls from Annex A and, if required, additional controls, comparing them against those in the 2013 version if a transition is in progress

Compares the controls determined in step b) with those in Annex A and verifies that no necessary control has been omitted

Produces a Statement of Applicability (SoA) that contains:

  • The necessary controls (Annex A and any additional) and their justifications
  • Controls that are included and their justification for inclusion
  • Controls that are excluded and their justification for exclusion
  • The status of implementation of each included control
  • Produces a risk treatment plan and obtains risk owners' approval of the plan and the residual risks
  • The SoA at 6.1.3 d) — High-Yield Topic

The Statement of Applicability is the single most tested artifact of Clause 6. The exam expects you to know that:

The SoA is required at 6.1.3 d)

The SoA must justify both inclusion and exclusion of Annex A controls — omitting a control is allowed but must be explained

The SoA must state the status of implementation for each included control (e.g., implemented, in progress, planned)

  • The SoA is documented information that must be maintained and reviewed
  • Risk Treatment Plan and Risk Owner Approval

The risk treatment plan documents what will be done, who will do it, with what resources, and by when. The plan and the residual risks must be approved by the risk owners — not by top management in general, and not by the implementer. Risk owner approval is a specific, mandatory signature in the standard.

Common Traps on 6.1.3

"The SoA lists only the controls that are implemented." Wrong — it lists all necessary controls, including those not yet implemented, with their implementation status.

"Controls can be excluded without justification." Wrong — exclusions must be justified.

"The risk treatment plan is approved by top management." Wrong — it is approved by risk owners.

"Risk treatment options are limited to mitigate and accept." Wrong — there are four options: avoid, modify, share, retain.

6.2 Information Security Objectives and Planning to Achieve Them

The organization must establish information security objectives at relevant functions and levels . The objectives must:

  • Be consistent with the information security policy (Clause 5.2)
  • Be measurable (where practicable)
  • Take into account applicable requirements and the results of risk assessment and risk treatment
  • Be monitored
  • Be communicated
  • Be updated as appropriate

The organization must keep objectives as documented information and plan how to achieve them by determining what will be done, with what resources, by whom, when, and how the results will be evaluated .

SMART Objectives

The criteria above map closely to the well-known SMART model:

  • SMART Element ISO/IEC 27001 Requirement
  • Specific Established at relevant functions and levels; consistent with policy
  • Measurable Must be measurable (where practicable)
  • Achievable Planned with resources, responsibility, and timeline
  • Relevant Takes into account applicable requirements and risk results
  • Time-bound "When" is part of the planning requirement

Plus two additional ISO-specific requirements: monitored and communicated , and updated as appropriate.

Good vs. Bad Objectives — Exam Examples

  • Bad Objective Good Objective
  • "Improve security." "Reduce phishing click rate from 12% to under 4% by Q4 2026."

"Train employees." "Deliver security awareness training to 100% of in-scope staff within 30 days of hire, with annual refreshers."

"Implement controls." "Implement MFA on all remote access pathways by 30 June 2026, verified by access logs."

Bad objectives are vague and unverifiable; good objectives are specific, measurable, time-bound, and tied to risk results.

How Clause 6 Connects to Other Clauses

Input from Used in 6.1/6.2 to...

  • 4.1 issues Identify risks and opportunities
  • 4.2 requirements Set risk criteria and objectives
  • 5.1 leadership Ensure risk owners are appointed
  • 5.2 policy Provide framework for objectives (6.2)
  • 5.3 roles Assign risk owners who approve treatment
  • 6.1 outputs Drive 7.2 competence, 7.3 awareness, 7.4 communication, 8.1 operational planning, 9.1 monitoring
  • 6.2 objectives Evaluated in 9.1 monitoring and 9.3 management review

Clause 6 is the pivot point of the entire standard. Everything before it sets the stage; everything after it depends on its outputs.

Exam Scenarios and Traps

Trap 1 : An option claims the SoA is optional. Wrong — it is required at 6.1.3 d).

Trap 2 : An option says risk acceptance criteria are determined after the assessment. Wrong — they are set before.

Trap 3 : An option lists only three risk treatment options. Wrong — there are four (avoid, modify, share, retain).

Trap 4 : An option states that objectives must always be measurable. Wrong — they must be measurable where practicable .

Trap 5 : An option says the risk treatment plan is approved by top management. Wrong — risk owners approve the plan and the residual risks.

Trap 6 : An option says controls can be excluded silently. Wrong — exclusions must be justified in the SoA.

Key Takeaways

Clause 6 plans the ISMS: risks/opportunities (6.1) and SMART objectives (6.2).

6.1.2 requires a documented risk assessment process with pre-defined risk acceptance criteria — the link to the risk-management chapter.

6.1.3 requires a Statement of Applicability with justifications for inclusions, exclusions, and implementation status, plus a risk treatment plan approved by risk owners.

6.2 objectives must be consistent with the policy, measurable (where practicable), monitored, communicated, and updated.

The four risk treatment options — avoid, modify, share, retain — are a must-know for the exam.