How to Write and Implement an Information Security Policy

A policy should be short, testable and put into practice through steps that produce records. Structure, sample sentences, the distinction from procedures and common mistakes.
Technical summary
Technology
ISO/IEC 27001 Clause 5.2
Topic
Policy writing
Level
Start
In this article8 sections

The auditor’s first question about the policy is usually, “Who has read this?” In most organizations, the answer is unclear: there’s a twelve-page text downloaded from the internet with the company name changed; it’s signed, but no process is linked to it. The information security policy is the top-level document setting out management’s direction and commitment. If it’s well written, it’s short, clear and workable; detailed rules are left to sub-policies and procedures. If it’s badly written, it turns into either a long text nobody reads or general sentences that don’t correspond to any actual practice.

What is the policy’s job?

ISO/IEC 27001 clause 5.2 expects four things from the policy. None of them says “write down all the rules”:

  • To set an information security direction consistent with the organization’s purpose and context.
  • To provide a framework for information security objectives.
  • To express a commitment to meeting applicable requirements and continually improving the ISMS.
  • To be communicated within the organization and available to interested parties as appropriate.

The key word here is “context”. The policy must not contradict the context analysis and scope definition carried out under clause 4. If the scope has one location and two processes while the policy says “all group companies”, the auditor notes this as an inconsistency. This is also a mistake you may come across: the policy is written once, the scope changes later, and nobody goes back to the policy.

Suggested structure (2–4 pages)

The policy should be short enough to be read in a board meeting. If it goes over four pages, there’s a procedure inside it.

Section Content
Purpose and scope Why the policy exists, and which locations, units and information it covers
Principles Confidentiality, integrity, availability; a risk-based approach; least privilege; legal compliance
Objectives framework How objectives are set and measured (e.g. annual objectives are approved in management review)
Roles and responsibilities Top management, ISMS manager, process and asset owners, all employees
Sub-policies References to documents on access, classification, acceptable use and so on
Non-compliance How policy violations are handled (link to the disciplinary process)
Review Owner, approver, effective date, review frequency

The “objectives framework” section is the one most often skipped. The policy doesn’t have to state the objectives themselves; it’s enough to say where objectives are set, who approves them and how they’re measured. Objectives change every year; the policy doesn’t. Without this distinction, the policy needs revising every year.

Take care with the “non-compliance” section too: if the disciplinary process isn’t defined in the HR regulations, the policy sentence “violations are subject to the disciplinary process” has nothing behind it. Check the existing regulations with HR before writing that sentence.

Examples of good and bad sentences

A policy sentence should be measurable, or at least verifiable. The auditor looks for a record behind every sentence.

To avoid Preferred
“The utmost importance is given to information security.” “Information security risks are assessed at least once a year, and the results are decided on in management review.”
“All systems are protected with the latest security measures.” “Security controls are selected based on the risk assessment and justified in the Statement of Applicability.”
“Employees receive the necessary training.” “All employees receive information security awareness training when they start and once a year; attendance is kept in HR records.”

The sentences in the left column can’t be tested. The ones on the right can. A phrase like “the latest security measures” means a policy violation at the first unpatched server and produces evidence against you. Don’t write what you can’t commit to.

Don’t confuse policy with procedure

A policy answers “what” and “why”; a procedure answers “who, how and when”. If details such as password length, backup time or log retention period are written into the policy, every technical change requires top management approval. These details should be kept in sub-policies or procedures. For document types, see the ISO 27001 documents guide.

A practical test: if a sentence in the policy becomes invalid when the IT team changes a server configuration, that sentence is in the wrong document. For example, “passwords must be at least 12 characters” belongs in the access control procedure; the policy only says “access is granted based on business need and the principle of least privilege; details are defined in the Access Control Policy”.

Think of the document hierarchy in three layers:

  • Top-level policy: Approved by management, 2–4 pages, reviewed once a year.
  • Topic-specific policies: Access, classification, acceptable use, suppliers, cryptography. Approved by the ISMS manager or the relevant process owner.
  • Procedures and instructions: Technical steps, screenshots, commands. Frequently changed, with a lower level of approval.

ISO/IEC 27002:2022 control 5.1 makes this distinction too: the top-level policy and topic-specific policies are treated separately. Setting approval authority by layer removes the problem of waiting for the general manager’s signature on every password change.

Putting the policy into practice

A policy that’s signed but not communicated is treated in an audit the same as one that was never written. The implementation steps must produce records:

  1. Approval: Top management’s signature or electronic approval, dated.
  2. Communication: An email or intranet announcement to all employees; for new employees, at onboarding.
  3. Acknowledgment: A read/accept record for user policies such as acceptable use.
  4. Training: The policy’s main principles in awareness training.
  5. Measurement: Reporting objectives and violations in management review.
  6. Review: Once a year or when significant changes occur.

In the communication step, the email itself is the evidence; keep the send date and recipient list. Compare the “all staff” distribution list with the HR list to check it really covers all staff. Employees on the production floor without an email account are the group most often missed; for them, a noticeboard announcement or a signed training attendance form is used.

Write down a definition of “significant change” too. Opening a new location, a company merger, a wider scope or a major security incident requires the policy to be reviewed without waiting for the annual calendar. If these triggers aren’t written down, review depends only on the calendar.

Common mistakes

  • Another organization’s name or out-of-scope locations left over from a template.
  • No version, effective date or owner information.
  • Sub-policies referenced in the policy never having been written.
  • The policy not being mentioned at all in the management review minutes.
  • The policy sitting only in the IT department’s shared folder, out of employees’ reach.

The last point looks simple, but it’s asked directly in audits. A randomly chosen employee is asked, “Where can you find the information security policy?” If the answer is “I don’t know”, the communication control isn’t working.

From the TISAX and IATF perspective

In TISAX assessments, what’s assessed is less the policy’s existence than whether it’s communicated and applied across the organization; if there are prototype protection or data protection objectives, the relevant principles should be in the policy set. Within IATF 16949, expectations for preparedness against cyber attacks and training can also be met through processes linked to the policy.

For organizations in the automotive supply chain, the practical route is to build a single policy set and meet TISAX and ISO 27001 requirements in the same documents. Two separate policy sets drift apart over time and produce contradictions in audits.

Frequently asked questions

Who should sign the policy?

Top management; usually the general manager or an executive authorized on behalf of the board.

Should the policy be public?

The standard expects the policy to be available to interested parties as appropriate. Publishing a short summary on the website is common practice.

If there’s a group policy, is a local policy needed?

If the group policy covers the scope, it can be used; a short supplementary document can be prepared for local legislation and scope differences.

To have your policy and supporting documents prepared specifically for your organization, take a look at our Information Security Policy and Procedure Package; for rules covering IT operations, our Corporate IT Policies and Procedures service.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles