Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

Control 6.2Information security objectives and planning to achieve them

Establish information security objectives at relevant functions and levels. They must be consistent with the policy, measurable where practicable, take account of applicable requirements and the results of risk assessment and treatment, be monitored, communicated and updated as appropriate, and be available as documented information. The organisation must determine what will be done, what resources are required, who is responsible, when it will be completed and how the results will be evaluated.

“Measurable where practicable” is the phrase organisations lean on hardest and are challenged on most. An objective such as “improve security awareness” states a direction, not an objective; the planning elements the clause then lists — what, who, when, how evaluated — cannot be completed against it.

The link to 9.1 is what makes this clause real: monitoring and measurement must evaluate the ISMS performance against these objectives. Objectives that cannot be measured produce a monitoring programme that measures activity instead.

How to put this in place

Objectives turn the policy into things that can be measured. Vague aims that nobody measures cannot show that the ISMS works.

  1. Choose a small number of objectives that follow from the policy and the risks.
  2. Give each a measure, a target, an owner, resources and a date.
  3. Approve them and tell the people who deliver them.
  4. Start measuring when the controls run.
  5. Review results at the management review and adjust.

Evidence an auditor usually looks for: a list of measurable objectives with owners and dates, evidence they are communicated, and results reviewed.

What is in the packs for this

From ISO 27001 Implementation & Certification Readiness. Each one helps with this requirement.