Servana

Free template · SV-POL-01

Information security policy

The top-level policy that sets out how your organisation protects its information, its systems and the personal information it holds, with POPIA built in.

PDF · 8 pages

What is an information security policy?

What it is

An information security policy is the top-level document that says how your organisation protects its information and systems. It sets out leadership's commitment, who is responsible for what, and the security rules everyone follows. Your more detailed policies sit underneath it.

ISO 27001 requires one, and it's often the first document a customer's security review asks for.

Why you need this template.

Why you need it

  1. 01

    One set of rules

    Everyone gets one clear statement of what's expected, and every other security policy hangs off it.

  2. 02

    Answers security reviews

    Customers ask for it in security questionnaires. An approved, current policy keeps deals from stalling.

  3. 03

    Meets ISO 27001 and POPIA

    ISO 27001 requires a top-level policy, and POPIA requires reasonable security measures. This shows yours.

  4. 04

    Every job has an owner

    Each responsibility gets a named owner, from the board to the Information Officer, so nothing falls between the cracks.

What's in the template.

What's inside

  • Document control and how-to steps, ready to fill in
  • Purpose, scope and a leadership policy statement
  • Roles from the board to the Information Officer, with guidance for small teams
  • 14 security requirement areas, from risk and access control to backups and people
  • MFA, patching, logging and access review timeframes you set yourself
  • POPIA section 22 breach notification built into incident management
  • Exceptions, non-compliance, related policies and a review log

How to make it yours.

How to use it

  1. 01

    Fill in your details

    Replace every highlighted [placeholder] with your own details, and set timeframes you can actually meet.

  2. 02

    Delete the guidance

    Read the grey guidance boxes, act on them, then delete them before you publish.

  3. 03

    Approve and share it

    Have leadership approve it, share it with everyone in scope, and review it at least once a year.

  4. 04

    Link your other policies

    It sits above your access control, acceptable use, incident response and other policies. Keep the list in section 8 current.

Get the information security policy.

It's free. Give us your first name and work email and it downloads straight away.

PDF · 8 pages

Questions, answered.

Questions

What should an information security policy include?

Its purpose and scope, leadership's commitment, roles and responsibilities, and the security requirements everyone follows: risk, access control, operations, suppliers, incidents, continuity and people. Then how exceptions are handled and how it's reviewed. This template covers all of these.

Does ISO 27001 require an information security policy?

Yes. Clause 5.2 of ISO/IEC 27001 requires top management to set an information security policy, keep it documented and communicate it. This template is a strong starting point, but your auditor will look at how you apply it, not only at the document.

How often should we review it?

At least once a year, and after any significant incident, organisational change or change in the law. The template has a review log to record each version.

Is it ready to use as it is?

Almost. Replace the placeholders with your own details, set timeframes you can meet, and delete the guidance boxes. It's general guidance, not legal advice, so have it reviewed before you adopt it.

All templates

Want it finished for you?

We tailor these policies and plans to how your business really works, and get the controls behind them ready for ISO 27001 or POPIA. Book a 30-minute call.