A password policy is a documented statement of your organisation's requirements for credential management. For most SMEs it is a one-to-two-page document that belongs in the staff handbook, the security policy, or both. Writing one is neither difficult nor time-consuming, but skipping it creates gaps in Cyber Essentials compliance, complicates insurance claims after incidents, and leaves staff without clear expectations.
What to Include
A complete SME password policy covers six areas:
- Scope: Which accounts and systems this policy applies to (all company accounts, cloud services, shared systems)
- Password requirements: Generated by the company password manager; minimum length; no personal information; unique per system
- Password manager: Which tool is designated, that all staff must use it for work credentials, how to get access
- MFA requirements: Which accounts require MFA and the accepted methods
- Change requirements: When passwords must be changed (on security concern, on a service breach notification, not on a fixed schedule)
- Prohibited actions: Sharing credentials, writing in plaintext, reusing personal passwords, emailing credentials
Drafting It in an Afternoon
A password policy does not need to be a lengthy document. For most small businesses, a clear, one-page set of rules is far more useful than a sprawling framework that nobody reads. You can get a working draft together in a single sitting by following a straightforward sequence.
- List your systems first. Before writing a single rule, jot down every system staff log into: email, accounting software, shared drives, social media accounts, any customer-facing tools. The policy needs to cover all of them, so knowing the full list stops you writing something that misses half your business.
- Decide on your minimum requirements. Work through each system and note whether it holds sensitive data, financial information or customer records. Higher-risk systems warrant stricter requirements, such as longer passwords or mandatory two-factor authentication.
- Write rules in plain language. Avoid technical jargon. Staff should be able to read the policy and act on it immediately, without needing to ask for clarification. Each rule should start with a clear instruction rather than a condition.
- Cover shared and personal accounts separately. Generic logins shared between colleagues are a common weak point in small businesses. Address them explicitly, even if your current position is simply to phase them out.
- Get a second pair of eyes on it. Ask someone outside your IT or management function to read the draft. If they find anything confusing, rewrite it before distributing.
Once you have a draft, circulate it to staff with a brief explanation of why the policy exists. Understanding the reasoning makes people far more likely to follow it.
Enforcing It Without Friction
A policy that frustrates staff will quietly be ignored. The aim is to set rules that are firm but practical, and to build enforcement into normal working habits rather than treating it as a separate discipline.
Set a review cycle and stick to it. Reviewing the policy once a year is usually sufficient for a small business, unless you take on new software, experience a security incident, or significantly change how your team works. Put a recurring reminder in your calendar so the review actually happens.
Be clear about what happens when the policy is breached. Staff need to know what is expected of them if they share a password, reuse credentials across accounts, or lose a device. The response does not need to be punitive, but it should be consistent and documented.
- For a first breach, a brief conversation and retraining is usually appropriate.
- For repeated or deliberate breaches, follow your existing disciplinary process.
- For incidents involving customer data, you may have legal reporting obligations under UK GDPR, so act quickly and take advice if needed.
Keep the policy current. Remove references to systems you no longer use, and add guidance whenever you introduce new tools. An outdated policy creates confusion about what actually applies. Treat it as a living document rather than something filed away after first publication.
Finally, make the policy easy to find. Staff cannot follow rules they have to hunt for. Keep a copy somewhere accessible, such as your company intranet or a shared drive folder that everyone can reach.
What to Avoid
- Mandatory rotation schedules: "Change your password every 90 days", NCSC and NIST explicitly advise against this; it produces weaker security
- Complexity rules that conflict with password managers: If staff use a password manager, complexity rules are enforced by the manager, restating them creates confusion
- Unrealistic requirements: Policies that cannot be followed will not be followed; work with what your tools actually support