Free tool · no signup

Security policy template generator

Pick the policies you need, set your own numbers for passwords, backups and patching, and get clear, short policies you can hand to staff, customers and auditors.

By the Bug Circuit security team · Last updated

Your company

Policies to write
  • Add your company name.
  • Name the person who owns these policies.
Your policies (Markdown)
Add your company name and a policy owner, and choose at least one policy.
  • These are plain templates to adapt, not legal advice. Remove anything you will not follow, because a policy you ignore is worse than none, and keep a record that staff have read it.
What security policies does a small business need? At minimum: acceptable use, passwords and multi-factor authentication, access control, backups and incident reporting. This tool writes each as a short, plain-English page with your own numbers, ready to paste into a document.

How it works

Why short policies

Customers, insurers and auditors increasingly ask to see written security policies, and a questionnaire that says "we have a password policy" is easier to answer with a one-page document. The policy that works is the one people can read in two minutes and that the company really follows. A long policy copied from a template that nobody follows is a liability, because it shows you knew what to do and did not do it. So each policy here is a single page of numbered statements, each short enough to be checked.

What you can choose

Eight policies are available: acceptable use, passwords and multi-factor authentication, access control, backup and recovery, incident reporting, updates and patching, devices and remote work, and suppliers and third parties. Your choices flow into the text. You set the minimum password length, whether multi-factor authentication applies everywhere or to important accounts, how often backups run and how long they are kept, how often you test a restore, the time limits for critical, high and other updates, and how fast incidents must be reported.

The defaults follow current guidance. Length matters more than complexity for passwords, there is no forced periodic change unless an account may be exposed (NIST SP 800-63B), passwords are checked against breached lists, and a critical patch is applied within days, not months. The tool warns when a number is out of line, for example a password minimum below 12 or a critical patch window above 14 days.

Using them

Copy the Markdown into your document system, name an owner who can answer questions, and set a review date. Remove anything you will not follow, because it is better to have fewer promises you keep. Make sure each person reads the policies when they join and once a year, and keep a record that they did. Security questionnaires and insurers usually accept a short policy with an owner and a date. These are templates, not legal advice, so adapt them to your business and have them reviewed if you are in a regulated sector.

Worked examples

A password policy line

Minimum length 14, multi-factor authentication on every account that supports it.

1. Passwords are at least 14 characters. Length matters more than symbols, so long passphrases are encouraged.
4. Multi-factor authentication is required on every account that supports it.

Your numbers go straight into the text, so the policy says what you actually do.

A backup policy with your choices

Daily backups, kept for 30 days, restore tested every 6 months.

1. Critical data is backed up daily.
2. Backups are kept for at least 30 days.
5. A restore of important data is tested at least every 6 months.

The tested restore is the line auditors ask about most, so make sure you do it.

The header every policy gets

Owner, effective date and review cycle.

| Company | Acme Ltd |
| Owner | Sam Lee, Owner |
| Effective | 2026-11-22 |
| Review | every 12 months |

An owner and a date make a policy something an auditor can accept.

Frequently asked questions

What security policies does a small business need?
Start with acceptable use, passwords and multi-factor authentication, access control, backup and recovery, and incident reporting. Add updates and patching, devices and remote work, and suppliers as you grow.
Are the policies legal advice?
No. They are plain templates to adapt. If you work in a regulated sector, or hold sensitive data, have a lawyer or compliance adviser review them.
Do I have to follow every line?
Yes, so remove what you will not do. A policy you ignore is worse than none, because it shows the company knew the right thing and did not do it.
Why no forced password changes?
Current guidance from NIST says to change passwords only when there is evidence of compromise, because forced changes push people to choose weaker, predictable ones. Use a password manager, unique passwords and multi-factor authentication instead.
How often should policies be reviewed?
At least once a year and after any incident or major change. The review date is in the header of every policy.
Will these satisfy a security questionnaire or SOC 2?
They are a good start for questionnaires. SOC 2 and ISO 27001 need more: evidence that you follow the policies, risk assessments and more detailed procedures. A short policy set is where most small firms begin.
How do staff acknowledge them?
Ask each person to read the policies when they join and each year, and keep a record, for example a signed list or a tick in your HR system.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Security Policy Template Generator · Bug Circuit