Policies, Standards, Procedures and Guidelines
four documents everyone mixes up, and how they fit together
A mature organization writes down what it expects and how it does things. The documents sit at different levels, and confusing them is a classic source of audit findings and employee frustration.
The hierarchy
- Policy: a short, management-approved statement of what must be done and why. It sets direction and responsibilities and rarely changes. Example: "Access to systems holding customer data must be restricted to authorized staff."
- Standard: mandatory specifics that support a policy. Example: "Passwords must be at least 14 characters and checked against a breached list. MFA is required for remote access."
- Procedure: step-by-step instructions for doing a task consistently. Example: how a manager requests, approves and records a new access.
- Guideline: recommended practice that is advice, not a rule.
- Baseline: a minimum secure configuration for a type of system.
A handy memory: policy is why and what, standard is how well, procedure is how exactly, guideline is how we suggest.
Characteristics of good ones
- Short and readable. A 60-page policy no one reads protects no one.
- Owned. Named owner, approver, version and review date.
- Approved at the right level, with leadership visibly behind it.
- Realistic. Written for how work really happens, or people will work around it.
- Enforceable and measurable, so compliance can be checked.
- Communicated and acknowledged, with training for the ones that affect people daily.
- Reviewed regularly, at least yearly or after major changes.
Typical security policies
Information security, acceptable use, access control, data classification and handling, password and authentication, remote working, incident response, backup, change management, vendor management, secure development and business continuity. Frameworks such as ISO/IEC 27002 and NIST SP 800-53 describe what these should cover.[1][2]
Exceptions
Sometimes a rule cannot be met. A formal exception process records the reason, the risk, any compensating controls, the approver and an expiry date. Untracked exceptions are just silent non-compliance.
Common mistakes
Copying a template without adapting it, policies that nobody can find, procedures that describe the ideal and not reality, never retiring old documents, and writing rules the organization has no ability to follow.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.