A short software installation policy template: approved and licensed software only, security software left on, and updates in line with Cyber Essentials.

Effective Policy Templates

This policy template is supplied in fully editable MS Word format and can be easily customised and edited. The document uses pre-defined style formatting throughout, with all text in Calibri font for improved readability.
The following document labelling is included in the footer:

• Policy number and title
• Information-classification
• Version
• Page number / total pages

alphaZ documents - beautifully designed, tried and tested policy templates. No junk, jargon or unnecessary content. Simple and usable policy templates developed over 25 years through practical use in the real world.

Further Reading

Further guidance on software and patching:

• Malware, Anti-Malware and Patching
• Cybersecurity
• Information Security Incidents and Ransomware
• Information Security knowledge base

Logo Update Service

Download this policy template with your company name and logo already added!
Document Preparation is included with the alphaZ subscription.

How to Download

This file is included in the alphaZ subscription. This policy is also included in the ISO 27001 Toolkit and every alphaZ ISO toolkit that covers ISO 27001, so the toolkit route gives you this file plus everything else you need in one download.

Need Help Implementing?

If you'd like this policy prepared for your organisation along with the rest of your company policies, or help with your information security risk assessment and treatment plan, our remote support services provide direct expert input from our team, by the day, by project, or on an ongoing basis.

Software Installation Policy Template

A software installation policy template making sure only approved and secure software is installed or used, that licences are managed, and that software is kept up to date.

The policy has Approved By and Date Approved fields and carries a Public information classification, so it can be shared with workers, clients and other interested parties.

What the Software Installation Policy Covers

• Approval - no software installed without approval, and new software checked before use
• Licensing - no unlicensed, pirated or cracked software
• Security software - antivirus and other security software never removed or deactivated
• Unsafe software - removed from all devices when requested and not reinstalled
• Free software - only installed once checked and approved, and known adware never installed
• Updates - operating systems and software patched and kept up to date, with automatic updates where possible and critical or high-risk updates applied promptly
• Auditing - regular software audits of all devices
• Reporting - software issues, suspected malware and suspected security breaches reported

Checked Against Cyber Essentials

The IT policies in the range have been checked against the Cyber Essentials requirements, so their rules on passwords, devices, access and updates do not contradict what a Cyber Essentials assessment asks for.

Using the Policy

Add your company name and logo, check each commitment matches what your organisation does and edit any that do not, then approve and date the policy and share it with workers and anyone else who needs to see it.

Who Needs a Software Installation Policy?

Organisations applying for Cyber Essentials, where security update management is one of the technical controls, organisations working to ISO 27001, and any organisation that wants control over what is installed on its devices.

Included in the ISO 27001 Toolkit

This policy is part of the ISO 27001 Toolkit and every alphaZ ISO toolkit that covers ISO 27001.

Works with the Software Procedure

The PP-8-03 Software Policy Procedure covers software management, the TT-8-03 Software and Malware toolbox talk briefs workers, and the same policy is included as the Software Installation Policy section of the PP-8-100 Information Security Policy Procedure.

Document Control

The footer carries the policy number and title, information classification, version and page numbers, and the approval fields record who approved the policy and when, so it can be controlled with the rest of your management system documents and listed on a document register such as the F-IMS20 Document Register.

Related Policies

• P-21 IT Equipment Policy - IT equipment
• P-114 Cyber Security Policy - cyber security
• P-40 Acceptable Usage Policy - acceptable use
• P-35 Information Security Awareness Policy - information security awareness
• P-113 Intellectual Property Policy - intellectual property
• P-29 Mobile Device Policy - mobile devices