Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An ISMS is the documented set of policies, processes, roles, and records through which an organisation manages information security risk deliberately rather than reactively.

What Is an Information Security Management System?
An information security management system is the machinery an organisation uses to decide what needs protecting, choose how to protect it, check whether the protection works, and correct it when it does not. The word that carries the weight is system. Buying a firewall is a control; deciding which risks justify a firewall, who owns it, how its effectiveness is measured, and what happens when the measurement is poor is a management system.
The concept is defined by ISO/IEC 27001, which is the standard against which an ISMS is certified. You can run one without certifying it, and plenty of organisations do.
Written out like that it sounds bureaucratic. In practice the useful part is the loop: assessment feeds treatment, treatment produces controls, measurement tests controls, and findings feed the next assessment.
An ISMS without a working risk assessment is a filing cabinet. The methodology should produce repeatable results, which means defined impact and likelihood scales, named risk owners, and criteria for accepting residual risk at a stated level of authority.
Two practical tests of whether the assessment is real. Does it change what the organisation does, or does the treatment plan always conclude that existing controls are adequate? And can a risk owner, asked at random, describe the risk they own without reading from the register? If either answer is uncomfortable, the system is documentation rather than management.
ISO/IEC 27005 provides guidance on the method, and ISO/IEC 27002 provides implementation guidance for the controls themselves.
The standard requires documented information where it is necessary for effectiveness, not a document for every activity. A workable set for a mid-sized organisation runs to roughly a dozen governing documents: scope, policy, risk methodology, risk register and treatment plan, Statement of Applicability, access control policy, supplier security policy, secure development policy, incident management procedure, business continuity arrangements, internal audit programme, and management review records.
Everything else should be the operational records those documents call for: access review evidence, training records, test reports, change approvals, incident logs. Auditors ask for records far more often than for policies, and an organisation with excellent policies and no records fails.
These two are the most commonly neglected requirements and the most diagnostic. Internal audit must be conducted by people independent of the activity audited, on a programme covering the whole ISMS over a defined cycle, with findings recorded and tracked. Small organisations use a competent external auditor or a reciprocal arrangement with another department; using the person who wrote the control is not acceptable.
Management review has a prescribed input list that includes audit results, performance against objectives, feedback from interested parties, risk assessment status, and opportunities for improvement. Minutes showing a discussion and decisions are the evidence. A review that occurred but was not minuted did not occur as far as a certification body is concerned.
Certification is a commercial decision, not a security one. It helps when clients, tenders, or regulators ask for evidence you cannot otherwise produce, and UK buyers increasingly expect an accredited certificate, so check that your certification body is accredited by UKAS.
An ISMS also supplies the evidence base for obligations that are not optional: the accountability principle and Article 32 security measures under UK GDPR, the NIS Regulations for operators of essential services, operational resilience rules in financial services, and client contract terms. Running the system without certifying it still delivers that.
Where organisations go wrong is treating the ISMS as separate from the engineering work. The system should be describing what the technical teams actually do, and the only reliable way to know that it does is to test. Our regulation and compliance services cover both building the system and proving the controls underneath it exist.
Only if someone requires it. Certification provides independent evidence for clients, tenders, and regulators, and UK buyers increasingly ask for an accredited certificate. Running an uncertified ISMS still gives you the risk management discipline and the evidence base for UK GDPR accountability. Certify when the commercial return justifies the audit cost and ongoing surveillance.
Wide enough to cover what your clients care about. A scope limited to one office or one product may pass certification but will be scrutinised during due diligence, and buyers routinely discount certificates that exclude the platform holding their data. Define scope by the services and information assets that matter commercially, then resource it properly.
It records a decision on every Annex A control: whether it applies, the justification, and how it is implemented. It is the document auditors review first, because it shows the link between the risk assessment and the controls in place. Excluding a control is acceptable when the justification is sound and consistent with the risk assessment.
Yes, and the requirements scale. A twenty-person company needs the same components but far less documentation: a tighter scope, a simpler risk methodology, fewer policies, and management review folded into an existing leadership meeting. The common failure at small scale is adopting a consultancy template built for a large enterprise and then being unable to maintain it.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.