Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The policy hierarchy separates governing documents by audience and authority: policies state intent, standards set mandatory requirements, procedures give steps, and guidelines advise.

What Is the Security Policy Hierarchy?
Most organisations have too many security documents and too little clarity about which of them anyone has to obey. The policy hierarchy fixes that by separating documents according to two questions: who approves this, and is it mandatory. Get those right and a 60-page document that nobody reads becomes a two-page policy, a handful of standards, and procedures that live with the teams who perform them.
The hierarchy is not bureaucracy for its own sake. It is what allows a password requirement to change without a board meeting, and a statement of principle to survive a change of technology.
| Document | Answers | Approved by | Mandatory |
|---|---|---|---|
| Policy | Why, and what we will and will not do | Board or executive | Yes |
| Standard | What specifically must be achieved | CISO or security governance forum | Yes |
| Procedure | How to do it, step by step | Process owner | Yes, for those performing the task |
| Guideline | What good practice suggests | Subject matter expert | No |
A worked example runs through all four. The access control policy states that access is granted on the basis of least privilege and reviewed regularly. The authentication standard requires multi-factor authentication on all remote and privileged access, with named acceptable factors. The joiners, movers, and leavers procedure tells an IT administrator exactly which systems to provision and in what order. A guideline suggests how to structure role groups in a new application.
Many organisations add a fifth document type: the baseline, a technical configuration specification for a platform, such as a hardened Windows Server build derived from CIS Benchmarks. Baselines sit alongside standards and change far more often, which is precisely why they should not be embedded in a board-approved document.
Approval authority is the practical reason. A policy approved by the board takes months to change; a baseline may need changing the week a vendor releases a new version. Putting a specific cipher suite into a board-level policy guarantees one of two outcomes: a policy that is out of date, or a board asked to vote on TLS configuration.
Audience is the second reason. Nobody in finance needs the server hardening baseline, and no system administrator should have to read fourteen pages of governance language to find the step they need. Awareness training works better when the acceptable use policy is short enough to be read in one sitting.
Clause 5.2 of ISO 27001 requires a single information security policy, approved by top management, appropriate to the organisation’s purpose, and communicated to everyone who needs it. Annex A control 5.1 then expects topic-specific policies underneath it, reviewed at planned intervals and after significant change. The 2022 edition uses exactly that phrase, “topic-specific policies”, to describe what older versions scattered across separate controls.
Auditors test three things beyond existence: that top management approved the policy, that staff can show they received and acknowledged it, and that the review dates have actually been met. Document control therefore matters as much as content. Every document should carry a version, an owner, an approval date, and a next review date, and the current version should be the one people can find.
Any mandatory requirement will eventually be impossible for some system to meet. If there is no exception process, teams simply break the standard silently, and the organisation loses visibility of its own risk. A workable exception record states the requirement not met, the business reason, a compensating control, an accountable owner, and an expiry date. Expiry is the part most often omitted and the part that matters most: permanent exceptions are policy changes in disguise and should be handled as such.
Reviewing the exception register is one of the best diagnostics available. Twenty exceptions against the same standard usually means the standard is wrong, not that twenty teams are negligent.
Document sprawl is the common failure. Ten to fifteen topic-specific policies cover most organisations: acceptable use, access control, cryptography, supplier security, incident management, business continuity, data protection, secure development, remote working, and physical security. Each should have a named owner, an annual review, and an explicit statement of who it applies to. Documents that have not changed in five years and cite systems you no longer run do more harm than good, because they teach staff that the policy set is theatre.
If you need a policy set that maps cleanly onto an audit, our regulation and compliance services align documentation with the controls auditors will ask you to evidence.
A policy states intent and principle, is approved at board or executive level, and changes rarely. A standard states the specific, measurable requirement that implements that intent, is approved by the security function, and changes as technology does. The policy says access must be controlled according to least privilege; the standard says which authentication factors are acceptable for privileged access.
One overarching information security policy plus roughly ten to fifteen topic-specific policies suits most organisations. Common topics include acceptable use, access control, cryptography, supplier security, incident management, business continuity, secure development, and remote working. More than that and staff cannot navigate the set; fewer and individual documents become too long and too general to act on.
Annually as a baseline, and additionally after any significant change such as a major incident, a new regulation, an acquisition, or a substantial architecture shift. ISO 27001 requires review at planned intervals and after significant change, and auditors check whether the stated review dates were actually met. Standards and baselines usually need more frequent review than the policies above them.
The requirement that cannot be met, the business justification, the compensating control reducing the residual risk, a named accountable owner, and an expiry date. Exceptions should be recorded centrally and reviewed periodically. A cluster of exceptions against the same requirement is a signal that the requirement itself is unrealistic and should be revised rather than repeatedly waived.
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.