“Improving information security” isn’t an objective. At the end of the period, nobody can say whether it was met or not, and the auditor sees this at first glance. Information security objectives are the shortest way to show management whether the ISMS is working; but only when they’re written to be measurable. Below we explain how to derive objectives in line with ISO 27001 clause 6.2 from the policy and risk assessment, examples of weak and good objectives, an objective planning card and how objectives link to clause 9.1 measurement.
How objectives relate to policy and risks
ISO/IEC 27001:2022 clause 6.2 requires information security objectives to be established at relevant functions and levels, and to: be consistent with the information security policy, be measurable where practicable, take into account applicable information security requirements and the results of risk assessment and risk treatment, be monitored, be communicated, be updated as appropriate and be available as documented information. The “be monitored” requirement was explicitly added in the 2022 revision.
This definition says objectives are fed from three sources:
- Policy: Commitments in the policy (such as confidentiality of customer information, service continuity) set the direction of objectives. For the policy itself, see the guide how to write an information security policy.
- Risk assessment: Risks that remain high and major actions in the risk treatment plan are the best candidates to become objectives.
- Requirements: Interested parties’ contractual and legal requirements (for example, an incident notification time) can directly give the acceptance threshold for an objective.
An objective that can’t be linked to any of these three sources is either unnecessary or in the wrong place. Take it off the list.
The elements of a measurable objective
A measurable objective is one where everyone reading it gives the same answer to “Was it met?” at the end of the period. For this, these elements must be written down:
- Indicator: What will be measured (for example, time taken to apply critical patches).
- Target value and threshold: The accepted value and the value below which action will be taken.
- Scope: Which group of assets or processes the indicator applies to.
- Timeframe: The date by which, or the period for which, the objective applies.
- Data source: Which system or record the value will be taken from.
- Owner: The person or role who does the measurement and owns the objective.
An element that may be missing is the data source. The objective is nicely written, but it isn’t clear who will pull the value from which report at the end of the period; in the end, someone types an estimated number into Excel. Scope is often skipped too: “servers” is written, but a virtual machine forgotten in a corner and missing from the inventory falls outside the measurement.
The phrase “measurable where practicable” in clause 6.2 acknowledges that some objectives may not be quantitative. The objective “Security requirements in the new ERP project will be documented before design approval” contains no number; but whether it’s been achieved is clearly verifiable. For a qualitative objective, a verifiable output and a date are enough.
Examples of weak and good objectives
The target values in the table are for illustration. Set your own values based on your current-state measurement and risk appetite; a value set without measuring is either met immediately or never.
| Weak objective | Problem | Well-written objective (example) |
|---|---|---|
| Increase awareness | No criterion or timeframe | All staff complete annual awareness training by the end of the year; the click rate in phishing simulations falls to half of the first measurement |
| Patch on time | “On time” undefined | Critical security patches applied within 14 days of release on internet-facing systems; the number of systems exceeding this time reported every quarter |
| Improve backups | Output unclear | At least one restore test per quarter for each critical system, with the results compared against the RTO target |
| No incidents at all | Uncontrollable, discourages reporting | Classification of reported security incidents completed within 1 business day |
| Audit suppliers | No scope or frequency | Annual security assessment completed by the end of September for all suppliers classified as critical |
The “no incidents at all” type of objective is particularly harmful. It isn’t within the organization’s control and creates unwanted pressure to suppress incident reporting: teams start not recording small incidents. What should be measured is the speed and quality of the incident management process. Silence isn’t security.
The backup row deserves a note too. A job that shows as “successful” in the backup software doesn’t mean restorable data; the most common situation in the field is application consistency (VSS, database log chain) being broken while the job shows green. That’s why the objective is written as “restore tested”, not “backup taken”.
Objective planning card
Clause 6.2 requires the answers to five questions when planning how objectives will be achieved: what will be done, what resources will be required, who will be responsible, when it will be completed and how the results will be evaluated. Gather these five questions for each objective on a single card; both implementation and auditing become easier.
Objective No. : ISO-2026-03
Objective : At least one restore test per quarter for each
critical system; result compared with the RTO
Source : Risk R-014 (recovery after ransomware),
policy art. 4 (service continuity)
What : 1) Update the list of critical systems
2) Prepare the test calendar
3) Set aside an isolated test environment
Resources : Storage for the test environment, 1 day of IT effort per month
Owner : System Administrator (implementation), ISMS Manager (monitoring)
Completion : End of period; quarterly interim check
Evaluation : Test records; systems tested / planned;
difference between measured recovery time and RTO
Reporting : Quarterly ISMS report, annual management review
Because the card shows which risk and policy article the objective comes from, it also provides traceability. Keep the number of objectives limited. A few meaningful objectives that management can really track do more than a twenty-row list nobody opens.
Monitoring, measurement and reporting
Objectives are defined in clause 6.2, measurement in clause 9.1. Clause 9.1 requires you to determine what will be monitored and measured, by what method, when and by whom, and when and by whom the results will be analyzed and evaluated. The “evaluation” row on the planning card is itself the answer to these 9.1 questions. Measurement results must be kept as documented information.
ISO/IEC 27004 (information security management — monitoring, measurement, analysis and evaluation) can be used as guidance in designing measurements. Practical tips from the field:
- Take data from systems wherever possible: the patch management tool’s report, the backup software’s job history, the training platform’s completion list. A hand-filled table both produces errors and raises questions about reliability.
- Fix the measurement method. If the definition of “critical patch” changes mid-period, the trend loses its meaning.
- Don’t confuse an objective indicator with a risk indicator. Key risk indicators (KRIs) give early warning that a risk is growing; an objective measures the management system’s commitment. For the distinction, see the KRI design guide.
- Prepare the report for decision-making: value, threshold, trend and recommended action. This report becomes a direct input to management review.
Clause 9.3.2 makes it mandatory to consider the extent to which information security objectives have been met, along with trends, in management review. How to design the meeting is explained in the guide management review.
What to do if an objective isn’t met
An objective not being met isn’t a nonconformity on its own. What the auditor looks at is whether the organization noticed the situation and what it did. The order we suggest:
- Catch the deviation early: Without a monthly or quarterly interim checkpoint, the deviation is only seen at the end of the period. By then, it’s too late.
- Analyze the cause: Is it a lack of resources, a wrong target value or a process problem? Process-related causes, such as a control not working, can become corrective actions under clause 10.2.
- Record the decision: A decision to increase resources, extend the deadline or revise the objective must be made by authorized management and written down with its justification.
- Don’t change the objective quietly: Lowering the target value at the end of the period without a decision record raises a serious question mark in the audit. The “be updated as appropriate” requirement in clause 6.2 requires updates to be deliberate and recorded.
Checklist
- Is each objective’s policy, risk or requirement source written down?
- Are the indicator, target value, timeframe, data source and owner defined?
- Does the planning card state what, resources, owner, timeframe and evaluation method?
- Have objectives been communicated to the relevant employees, and is there evidence of this?
- Are measurement results kept and reported to management review?
To design objectives and indicators together with management reporting, see our management review and KPI design service; to address objectives as part of setting up an ISMS, see the ISMS setup page. The official introduction to the standard is on the ISO/IEC 27001 page.
Frequently asked questions
How many information security objectives should we set?
The standard doesn’t give a number. A small number of objectives that management can track regularly and that link directly to the policy and significant risks does more than a long list nobody follows.
Does every objective have to be numerical?
No. Clause 6.2 requires objectives to be measurable where practicable. A qualitative objective is also accepted; however, whether it’s been achieved must be clearly verifiable, and it must have a completion date.
If an objective isn’t met, is a nonconformity written in the audit?
An objective not being met isn’t a nonconformity on its own. But failing to notice the deviation, not analyzing its cause or changing the objective without a record can lead to a finding under clause 6.2, 9.1 or 10.2.
Are objectives and KPIs the same thing?
No. A KPI is an indicator; an objective includes a value, timeframe, owner and plan tied to that indicator. An objective can be tracked with one or several KPIs, but not every KPI is an objective.