Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Clause 6.2 Information security objectives and planning to achieve them
Mandatory requirement Documented information required
What it means in plain language
Set measurable security objectives that support your policy and risk results, and plan how to reach them: what will be done, with what resources, by whom, by when and how results will be measured. Keep them updated and communicated.
Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.
Documented information
Information security objectives.
Why this requirement matters
Owners should write objectives that are measurable, owned, resourced, and visibly linked to policy commitments and risk outcomes. Effective objective setting distinguishes between an ambition and an objective: the latter needs a target, a baseline or method, a due date, and a named person accountable for progress. In practice, objectives are living management tools, updated when risk, scope, or business priorities change.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
An objective is written as a broad intention, such as “improve security,” without measurable target, owner, deadline, or method for tracking performance.
Progress is reported informally, but no baseline, trend, or status evidence exists to show whether the objective is being achieved within the planned period.
Objectives exist in a standalone list but are not reviewed after scope, risk, or resource changes, so they drift away from current priorities.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Write each objective so a reader can test it: what will be achieved, by when, and how success will be measured. Examples include completion rates, patching timeliness, training coverage, review closure times, or supplier assessment turnaround. Keep the wording specific enough that progress can be tracked from records rather than opinion, and align it to the security policy and risk treatment priorities.
Assign one accountable owner per objective, with supporting roles named only where needed for delivery or measurement. Record the required resources, such as tooling, staff time, budget, or external support, so under-resourcing does not become a hidden reason for delay. If an objective depends on another team, note the dependency and the escalation route if dates slip.
Establish a practical cadence for monitoring, such as monthly operational review and formal management review reporting. Capture baseline, current status, variance, and corrective action if performance falls behind plan. If an objective is revised, record why the target changed, who approved the change, and whether the original measure remains relevant to the current ISMS context.
Use management review outputs to keep objectives live: review whether each objective still supports the policy, reflects current risk, and has enough resources. If an objective is consistently met, consider raising the target or replacing it with a more meaningful measure; if it is missed repeatedly, document the root cause and the adjustment needed.
What an auditor will ask to see
An objectives register showing target, measure, owner, deadline, resources, and current status.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.