How to write security policies people actually follow
3 min read · Certifyi compliance team · Updated July 2026
Short answer
A policy is only useful if the behaviour it describes is what actually happens. Auditors test this by asking staff what they do and comparing it to the document. Downloaded templates fail that test because they describe an organisation you are not.
The policy set most frameworks expect
Information security policy (the umbrella)
Access control
Acceptable use
Incident response
Business continuity and disaster recovery
Change management
Vendor and third-party management
Data classification and retention
Secure development
Risk management
What makes a policy fail in practice
The recurring problems
Copied from a template describing controls you do not have
Written for a company of 500 when you are 40
Never communicated, so staff cannot describe their obligations
No named owner, so it is never updated
Aspirational: it describes intent rather than current practice
Writing one that holds up
Describe what you actually do today, then improve the practice and update the policy
Keep each policy short enough that people will read it end to end
Name an owner and a review date on every document
Get explicit acknowledgement and keep the records as evidence
Review whenever the underlying practice changes, not only annually
The honest tension
There is a real tension between writing what you do and writing what a framework expects. Resolve it by changing the practice, not by writing a policy you cannot honour.
An auditor who finds a policy requiring quarterly access reviews and no evidence of any review will raise a finding. A policy stating annual reviews, with evidence of annual reviews, passes. Overpromising in documentation is a self-inflicted finding.
Key takeaways
Policies must describe actual practice, not aspiration.
Auditors verify by asking staff, not just reading documents.
Every policy needs an owner, review date and acknowledgement record.
Do not promise a cadence you cannot evidence.
Frequently asked questions
Can we use policy templates?
As a starting structure, yes. They must then be rewritten to reflect your actual environment and practice.
How long should a policy be?
Short enough to be read. Two to four pages is usually plenty for a startup.
How often should they be reviewed?
At least annually, and whenever the practice they describe changes materially.
Do staff need to sign them?
You need evidence of acknowledgement. Electronic acceptance with a date and name is standard.