Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.
What it is
Control operation is the day-to-day running of the controls you've chosen. It's where most of the organisation meets the ISMS, usually without noticing, because well-designed controls look like normal work.
The business owns its controls, and control owners are responsible for the evidence their controls produce. The security or GRC function provides the framework, oversight and challenge, and checks that the evidence exists.
What the standard asks
Clause 8.1 asks you to plan, implement and control the processes needed to meet the standard's requirements and carry out your risk treatment, by:
- setting criteria for those processes and running them in line with the criteria
- keeping enough documented information to be confident they've been carried out as planned
- controlling planned changes and reviewing the consequences of unintended ones
- making sure externally provided processes, products and services relevant to the ISMS are controlled
What good looks like
- Every control has a first-line owner who knows it's theirs and what it involves.
- Evidence is a by-product. Evidence of a control is really evidence of review: an email, a meeting minute, a timestamped approval in a change record. It's produced as the work happens.
- Evidence is easy to find, filed by a predictable naming scheme so anyone can retrieve a quarter's worth in minutes.
- Change is controlled, so a new system or process gets the same treatment as the old one.
- Suppliers are included. Where a supplier runs part of a control, you know which part and how you check it.
Evidence an auditor will ask for
- Records produced by each control: approvals, reviews, logs and reports
- Change records for systems and processes in scope
- Supplier agreements and the checks you carry out on them
Common failure modes
- Evidence gathered in a panic. Screenshots collected the week before the audit, without dates or context.
- Security runs everything. Controls operated by the security team on behalf of everyone else don't scale, and don't show the business owns its risks.
- Outsourced and forgotten. The managed service provider runs half your controls and nobody has looked at how.
- Change outruns the ISMS. New systems arrive without anyone checking which controls apply.
How it connects
Feeds from
- Control selection, which defines the controls
- Policies and standards, which set expectations
Feeds into
- Metrics, which measure whether controls work
- Security events, when something goes wrong
- Assurance and audit, which test the evidence
Where it sits in the plan
Stage: Do. Operational teams run the controls as part of normal work. If they were designed well in Plan, Do is mostly about checking that evidence is being produced and filed as intended.
The plan in the main article shows how this fits with everything else, and the bootstrapping guide covers each stage in detail.
Resources
Tom Whipp is the founder of RiskQuilt. He spent around thirty years in cyber and technology risk in UK financial services, including CISO and Director of Technology Risk roles.