Help for owners
A customer asked for my written security policies and I have none
Short answer
Customers asking for policies mostly want to see that someone decided how security is handled. Write short, honest documents that describe what you really do, for example who has access, how you back up and what happens in an incident. Do not copy a template that promises things you do not do.
Does this sound like your situation?
- A prospect's form asks for an information security policy, an access policy and an incident plan.
- I have security habits but nothing written down.
- A downloaded template has pages of promises I cannot keep.
- Nobody in the company is named as responsible for security.
- The deal is waiting on documents.
Why does this happen?
The customer cannot inspect you, so they ask for paper
A written policy shows you thought about the topic and who is responsible. It is a quick way for a buyer to filter suppliers.
Small companies work from habit
Good practice often exists in people's heads. Without writing it down, nobody can prove it, and a new hire repeats the mistakes.
Templates describe a bigger company than yours
A long policy that says 'all laptops are encrypted' when half are not turns a document into a false claim, which is worse than having none.
Security is often left to one person
The NCSC's small business guide says cyber security should not rest with one person and that every member of the team should realise it is everyone's business.
Confirmed by ncsc.gov.uk
There are free starting points for small firms
NIST's small business cybersecurity pages offer quick-start guides, guidance on topics such as multi-factor authentication and a guide for solopreneurs.
Confirmed by nist.gov
What can I do about it today?
- Ask which documents they actually needRequest the exact list and the format. Often a few pages are enough, and a security questionnaire may be accepted instead.
- Write down what you really doWho has access to what, how passwords are handled, how backups are done and how a problem is reported. Plain sentences are fine.
- Name one person as responsibleA named owner for security questions, and a deputy.
- Mark gaps honestly as planned'This is planned' is acceptable. A false statement is not, and it can come back as a contract problem.
- Have the owner of the business approve itA date and a signature or approval line show it is real.
- Keep it short and review it laterA short true policy beats a long copied one. Put a review date on it.
When should I bring someone in?
- The customer's list asks about technical controls you are unsure you have.
- You need to know what is actually true before you write it.
- A contract clause makes the policy binding.
How do I handle it?
- Check what is true firstI look at access, backups, updates and how you handle incidents, so that the documents describe reality.
- Draft in your wordsShort documents, written for your team size, with gaps marked as planned.
- Turn gaps into a small planA list of the cheapest improvements, such as a second sign-in step and tested backups, in the order they reduce risk.
- Prepare the evidenceScreenshots and settings that show the claims are real, so that a customer's follow-up questions are easy.
- Leave legal wording to your lawyerI cover the technical statements. Contract and legal text stay with your adviser.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I use a free template?
As a starting layout, yes, but delete everything that is not true for you. A policy that overstates what you do can hurt more than having none.
How long should it be?
Short enough that your team has read it. A few honest pages usually serve a small company better than a long document nobody follows.
Does this replace a security certificate?
No. Policies are the base that questionnaires and certificates build on, and a customer may still ask for more.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.