Demo

How to write an information security policy

Definition, content, a detailed template outline, official French references and a seven-step drafting method: how to write a useful information security policy and keep it alive.

· 14 min read
Illustration: a stack of glass documents, the top one orange

An information security policy is the reference document, approved by senior management, that sets an organisation's security objectives, organisation and rules. It derives from risk analysis and applicable obligations, and is then broken down into topic-specific policies and procedures that everyone can apply.

In France it is called a PSSI (politique de sécurité des systèmes d'information). This guide gives you a template outline detailed chapter by chapter, reviews the official French references and proposes a seven-step drafting method, all the way to the annual review.

01

Information security policy: definition

An information security policy answers three questions: what are we protecting and why (stakes, security needs), who is responsible for what (organisation), and which rules apply (principles and requirements). It covers the whole information system, including people, premises, suppliers and cloud services, not just servers.

It is neither a technical procedure nor an acceptable use policy. It is the top-level document: it sets the direction, and more operational documents explain how. In an ISO 27001 information security management system, it is the information security policy required by the standard, supplemented by topic-specific policies.

The 4 pillars of information security

The needs a policy protects are often summed up in four criteria, known in France by the acronym DICP:

  • Availability: information and services are accessible when needed;
  • Integrity: information is not changed or destroyed without authorisation;
  • Confidentiality: only authorised people can access it;
  • Proof, or traceability: you can find out who did what, and when.

The policy does not set the same level for everything: a brochure website mainly needs availability, a patient record needs very strong confidentiality and integrity. Risk analysis tells you where to set the bar.

02

What is an information security policy for, and is it mandatory?

A well-written policy delivers three very practical benefits:

  • Alignment of management, IT and business units on a chosen level of security, instead of case-by-case decisions;
  • An enforceable basis for rules: you cannot require multi-factor authentication or refuse a cloud service without an approved policy;
  • Proof for auditors, customers, insurers and authorities that security is managed.

Is an information security policy mandatory?

There is no general obligation: a small company outside all the frameworks below can legally do without one. But the list of organisations concerned keeps growing, and the texts do not all say the same thing. Some require a policy document by name, others set out what the policy must contain, others require measures that presuppose a written policy.

What each text requires in terms of a security policy
TextWho is concernedWhat it requires
French military programming law (Defence Code, art. L. 1332-6-1)Operators of vital importance (OIV), for their critical information systemsThe sector orders implementing it make it rule no. 1: draw up, maintain and apply a security policy, formally approved by management, with at least an annual report on its implementation, available to ANSSI (for example the order of 10 March 2017 for the nuclear sector).
French NIS 1 regime (order of 14 September 2018)Operators of essential services (OSE), for their essential information systemsRule no. 2: a network and information system security policy approved by management, and at least an annual report on its implementation, the risks and the security level. This regime still applies until the NIS 2 transposition law is adopted.
NIS 2 (Directive (EU) 2022/2555, Art. 20 and 21)Essential and important entities in 18 sectorsArticle 21 lists "policies on risk analysis and information system security" first; Article 20 requires management bodies to approve the measures. In France, transposition goes through the "Resilience" bill, adopted by the Senate on 12 March 2025 and scheduled for debate in the National Assembly from 9 November 2026 (legislative file).
Implementing Regulation (EU) 2024/2690Digital service providers covered by NIS 2: cloud computing, data centres, managed and managed security services, DNS, online marketplaces, search engines, social networks, trust services…The policy's content is spelled out (point 1.1 of the annex): security objectives, commitment to continual improvement and resources, roles, topic-specific policies, indicators, date of management approval. It is reviewed at least once a year and after significant incidents.
PSSIE (circular no. 5725/SG of 2014)French ministries and the state public bodies they overseeApplication of the state security policy and its rules, adapted by each ministry (see section 4). Local authorities are not covered.
DORA (Regulation (EU) 2022/2554, Art. 9)Banks, insurers, asset managers and other financial entities"Develop and document" an information security policy defining rules to protect the availability, authenticity, integrity and confidentiality of data and ICT assets.
ISO/IEC 27001:2022 (clause 5.2)Organisations seeking certificationTop management establishes an information security policy suited to the organisation's purpose, setting objectives or a framework for them, committing to meet applicable requirements and to continual improvement; it is documented, communicated internally and available to interested parties.
French HDS certification (2024 framework)Health data hosting providersRequirement no. 1 calls for an ISO 27001-certified information security management system, and therefore the clause 5.2 policy.
GDPR (Art. 24 and 32)Every controllerAppropriate technical and organisational measures and, where proportionate, "appropriate data protection policies". No security policy by name, but a written policy is the simplest way to demonstrate compliance.
CaRE programme (French healthcare)Healthcare facilities applying for fundingThe national digital health agency lists "a security policy" among the prerequisites and asks for the policy document (February 2026 webinar).

In practice, even without an obligation, customers ask for the policy in their security questionnaires and cyber insurers ask for it too.

03

Information security policy template: a detailed outline

There is no mandatory outline, but solid policies share the same structure: a governance foundation, then rules by domain, then control and review arrangements. The template below follows that logic and the themes of ISO 27002:2022, which makes mapping to an ISO 27001 audit easier. Expand each chapter to see what it should contain.

Policy template Template outline for an information security policy
0 / 19 chapters open
A · Governance
00 Document control
What the chapter contains
  • Version, date, owner (often the CISO) and approver (senior management)
  • Distribution list and document classification
  • Revision history
01 Purpose, scope and audience
What the chapter contains
  • Entities, sites and systems covered, including cloud and suppliers
  • People concerned: employees, temporary staff, subcontractors
  • How it relates to other documents (topic-specific policies, acceptable use policy, procedures)
02 Context, stakes and references
What the chapter contains
  • Missions and business assets to protect
  • Security needs: availability, integrity, confidentiality, traceability
  • Applicable obligations: NIS 2, GDPR, ISO 27001, sector rules, contracts
03 Organisation and responsibilities
What the chapter contains
  • Role of senior management, the security committee, the CISO, IT and the DPO
  • Asset owners and data controllers
  • Obligations of users and suppliers

Sample ruleEvery critical application has a named business owner who approves its security needs and accepts its residual risks.

04 Risk management
What the chapter contains
  • Chosen method (EBIOS Risk Manager, ISO 27005…) and scales
  • Acceptance criteria and who may accept a risk
  • How often analyses are updated
B · Rules by domain
05 Human resources security
What the chapter contains
  • Joiners, movers and leavers
  • Awareness, training and acceptable use policy
  • Confidentiality clauses and sanctions

Sample ruleA staff member's access is disabled no later than their last day.

06 Asset management and classification
What the chapter contains
  • Inventory of assets and their owners
  • Classification levels and labelling rules
  • Removable media, wiping and disposal
07 Access control and identity
What the chapter contains
  • Least privilege and periodic access reviews
  • Multi-factor authentication, passwords
  • Administrator and service accounts

Sample ruleMulti-factor authentication is mandatory for all remote access and all administrator accounts.

08 Physical and environmental security
What the chapter contains
  • Secure areas and physical access control
  • Technical rooms, power, cooling
  • Protection of equipment off-site
09 Operations security
What the chapter contains
  • Backups and restore tests
  • Updates, vulnerability management, malware protection
  • Logging, monitoring, change management

Sample ruleCritical vulnerabilities exposed to the Internet are fixed or mitigated within seven days.

10 Networks, remote working and mobility
What the chapter contains
  • Network segmentation and filtering
  • Remote access and remote working
  • Mobile devices and Wi-Fi
11 Cryptography
What the chapter contains
  • When encryption is mandatory
  • Recommended algorithms and products
  • Key and certificate management
12 Security in projects and development
What the chapter contains
  • Security by design and project risk analysis
  • Security accreditation before go-live, where applicable
  • Secure development and testing
13 Supplier and cloud relationships
What the chapter contains
  • Contractual requirements and security assurance plan
  • Supplier assessment before and during the contract
  • Data location and reversibility
14 Incident management
What the chapter contains
  • Reporting, triage and escalation
  • Mandatory notifications (data protection and sector authorities)
  • Lessons learned
15 Business continuity and recovery
What the chapter contains
  • Recovery objectives for each critical activity
  • Continuity and recovery plans
  • Regular exercises and tests
C · Control and review
16 Compliance, control and audit
What the chapter contains
  • Internal and external audits
  • Steering indicators
  • Management review
17 Exceptions, sanctions and review
What the chapter contains
  • Exception process: justification, accepted risk, duration
  • Sanctions for breaches
  • Review frequency and triggering events

Sample ruleEvery exception is granted for one year at most and reassessed when it expires.

18 Appendices
What the chapter contains
  • Glossary
  • List of topic-specific policies and procedures
  • Mapping to ISO 27001 / 27002 and NIS 2
Indicative outline, aligned with the themes of ISO 27002:2022. Adapt it to your organisation's size and risks.

Adapt this outline to your size: an SME will merge several chapters, a group will point each domain to a topic-specific policy. The golden rule stays the same: every requirement must be verifiable. "Passwords must be strong" cannot be checked; "multi-factor authentication is mandatory for all remote access and all administrator accounts" can.

04

Official references in France: ANSSI guide, PSSIE and PGSSI-S

ANSSI's policy drafting guide

The French reference guide was published in March 2004 by DCSSI, which became ANSSI in 2009. It proposes a four-phase method (preparation, strategic elements, choice of security principles, finalisation and approval) and a catalogue of security principles by domain. It is still listed among the resources on ANSSI's security rules page, but has not been updated since: the method remains sound, the technical references have aged. For controls, supplement it with ISO 27002:2022 (93 controls in four themes) and ANSSI's IT hygiene guide (42 measures).

PSSIE, the French state's security policy

The PSSIE was introduced by the Prime Minister's circular no. 5725/SG of 17 July 2014. It applies to ministries and their public bodies, which adapt it into their own ministerial policy. ANSSI now presents a digital security governance framework for the state that is meant to replace the 2014 circular eventually; until then, both coexist, particularly for security rules.

PGSSI-S for healthcare

In the French health and social care sector, the general information system security policy for healthcare (PGSSI-S), published by the national digital health agency, provides a body of frameworks and guides. Some frameworks are made binding by ministerial order, others are recommendations. The PGSSI-S sets the sector framework; each facility's own policy sets its organisation and rules.

05

How to write an effective information security policy in 7 steps

Writing a policy is not a writing exercise: it is a project, with a sponsor, contributors and a timeline. ANSSI's drafting guide organises it in four phases: prepare the project, define the strategic elements (scope, stakes, obligations, security needs, threats), choose the principles and write the rules, then finalise and get approval. Here is the approach we recommend, which follows that logic and the ISO 27001 continual improvement cycle.

  1. Frame the project. Appoint a sponsor in senior management and a lead, often the CISO. Set the scope (whole organisation, a subsidiary, a site) and the contributors: IT, DPO, legal, HR, procurement, business units.
  2. Take stock. List obligations (NIS 2, GDPR, contracts, sector frameworks), existing documents and actual practices.
  3. Analyse the risks. Identify business assets, their availability, integrity, confidentiality and traceability needs and feared scenarios. A risk analysis, for example with the EBIOS Risk Manager method, provides the rationale for each rule.
  4. Set objectives and principles. Turn risks into security objectives, then principles by domain, using the template above.
  5. Write verifiable rules. For each rule: who it applies to, what is expected, who is responsible and how it is checked.
  6. Get management approval. Present the policy to the executive committee, with the resources required and the residual risks. Management's signature gives the document its authority.
  7. Publish, apply and check. Publish the policy, break it down into an acceptable use policy and procedures, raise awareness, then measure compliance and schedule the review.

What makes a policy effective

  • it is signed by senior management, which commits resources, not just by IT;
  • every rule stems from an identified risk or obligation, not from a template found online;
  • the top-level document stays short and moves details to topic-specific policies;
  • every rule is verifiable: a scope, an owner, a way to check it;
  • it provides for its own indicators, exceptions and reviews, as the most recent texts require (at least an annual review for regulated operators).
Lifecycle A security policy is never written once and for all
  1. Context, obligations and risk scenarios: the rationale for every rule.

  2. Objectives, principles and verifiable rules, written with IT, the DPO, HR and business units.

  3. Senior management approves and signs the policy, accepts residual risks and commits resources.

  4. Publication, acceptable use policy, topic-specific policies and staff awareness.

  5. Indicators, audits, assessment campaigns and exception tracking.

  6. At least once a year, and after a major incident or significant change.

The cycle starts again at every review: new risk analysis, new approved version, new rollout.
06

From the policy to topic-specific policies and procedures

A policy that tries to say everything becomes unreadable. Good practice is to organise documentation as a pyramid, which the CNIL also recommends for data protection policies: a management document, broken down into topic-specific policies and then procedures.

  • The top-level policy: objectives, organisation, main principles. Approved by senior management.
  • Topic-specific policies: access control, backup, vulnerability management, remote working, supplier relationships, secure development. Approved by the security committee.
  • Procedures and work instructions: how to create an account, how to restore a backup. Owned by the teams.
  • The acceptable use policy: rules for users, in their language. ANSSI's guide to IT acceptable use charters points out that, in France, it must be accepted by users or annexed to the internal regulations, after consulting staff representatives, before it can be enforced.

Supplier requirements deserve special attention: they feed your contracts, security assurance plans and third-party risk questionnaires.

07

Keeping the policy alive: reviews, exceptions and indicators

A policy is only useful if it is applied and kept up to date. Three mechanisms help.

Reviews

Plan at least an annual review. The CNIL also recommends at least an annual management review of security, to take stock and decide on resources. Trigger a revision after a major incident, a reorganisation, a merger, a regulatory change or a significant change to the information system. Each version should be dated, approved and archived.

Exceptions

There will always be a business application that cannot meet a rule. Rather than turning a blind eye, formalise the exception: rule concerned, justification, risk accepted by a named owner, compensating measures and expiry date.

Indicators

Measure how a few key rules are applied: share of administrator accounts protected by multi-factor authentication, time to fix critical vulnerabilities, success rate of restore tests, share of critical suppliers assessed. These indicators feed the security committee and the review.

08

Common mistakes in an information security policy

  • Copying a template without adapting it: a sample policy found online knows nothing of your risks or constraints. Auditors notice quickly.
  • Writing unverifiable rules: "secure", "ensure", "where possible".
  • Leaving out senior management: a policy signed only by IT does not bind business units.
  • Putting everything in one document: a hundred pages of technical detail nobody reads.
  • Neglecting suppliers and the cloud: much of the information system is now run by third parties.
  • Never revising it: a 2019 policy ignores widespread remote working, NIS 2 and the use of AI.
09

Managing your policy in a tool rather than a static document

The signed document remains essential. But to know whether the policy is applied, you need to turn its rules into requirements that can be assessed site by site or subsidiary by subsidiary, and track gaps in an action plan: that is the job of the IT security plan, which says who does what, and by when. That is the point of a governance, risk and compliance approach.

In Phinasoft, the policies editor lets you bring in your security policy: you define your security objectives, enter its structure and import your requirements, then enrich each requirement (links to other frameworks such as ISO 27001 or NIS 2, expected evidence). These requirements are then used to launch compliance campaigns or questionnaires, and successive versions of your policy are kept for your reviews. To see how your own policy would fit, you can request a demo.

Summary

01

A management document

The policy sets security objectives, organisation and rules. It is approved and owned by senior management, not just by IT.

02

Driven by risk analysis

Rules are chosen according to real risks and applicable obligations (NIS 2, GDPR, ISO 27001, sector rules), then broken down into policies and procedures.

03

A living document

At least an annual review, indicators, recorded exceptions: a policy that never changes soon stops being applied.

Frequently asked questions about the information security policy

What is an information security policy?

An information security policy is the reference document that sets the security objectives, organisation and rules an organisation applies to its information system. It is approved by senior management, based on risk analysis, and broken down into topic-specific policies and procedures. In France it is called a PSSI.

Is an information security policy mandatory?

No law requires one from every company. It is, however, explicitly required in France from operators of vital importance for their critical systems and from operators of essential services, from central government bodies (PSSIE) and from financial entities subject to DORA. ISO 27001, and therefore French HDS certification, requires an information security policy. NIS 2 lists such policies first among the expected measures; in France, its transposition bill was still before Parliament in November 2026.

How do you write an effective information security policy?

Start from risk analysis and applicable obligations, not from a copied template. Have senior management sponsor and sign the document. Keep the top-level policy short (objectives, organisation, principles) and move details to topic-specific policies. Write verifiable rules, each with an owner and a way to check it. Finally, plan indicators, an exception process and at least an annual review.

What are the 4 pillars of information security?

In France they are often summed up as DICP: availability (information is accessible when needed), integrity (it is not changed without authorisation), confidentiality (only authorised people can access it) and proof, or traceability (you can tell who did what). The policy sets the level expected for each one according to the stakes.

What is the difference between a security policy and an IT acceptable use policy?

The security policy covers the whole organisation: it sets objectives, responsibilities and security rules. The acceptable use policy is a shorter document for users, describing their rights and duties. It derives from the security policy; in France, it is usually annexed to the company's internal regulations so it can be enforced.

Who writes and who approves the policy?

The CISO usually leads the drafting, with IT, the DPO, legal, HR and business units. Approval lies with general management or the executive committee, which signs the document and commits resources. Without that approval, the policy lacks the authority it needs to be applied.

How often should the policy be reviewed?

At least once a year is common practice, and the French data protection authority (CNIL) recommends at least an annual management review of security. The policy should also be revised after a major incident, a reorganisation, a new regulatory obligation or a significant change to the information system.

Is there an official template?

ANSSI published a guide to drafting information security policies in 2004, with a method and a list of security principles. The French state has its own policy (PSSIE) and the healthcare sector has the PGSSI-S. These are useful starting points, but a policy must always be adapted to the organisation's context and risks.

How long should the policy be?

There is no standard. A readable top-level policy is often fifteen to thirty pages long, with technical details moved to topic-specific policies and procedures. A short policy that is applied and checked beats an exhaustive one nobody reads.

Sources (20)

A platform and service that adapt to you

Our platform is designed for fine-tuned configuration and broad adaptability to your needs.