ICT Purchasing policy
The purpose of this policy is to detail the Council's IT software, hardware & services purchasing policy. In conjunction with the ICT Purchasing Standards, it provides the requirements and information for software installations within Ashfield District Council from a technical and security standpoint. This policy will be referenced by a top level Governing Policy.
Who does this policy apply to?
- Ashfield District Council employees
- Third party suppliers of software/systems
Why have a software purchasing policy?
- To ensure that software can be supported by existing resources and documented procedures
- To allow centralized control of all software for ease of installation and to speed up the process of upgrading or patching
- To ensure software is installed in such a way that does not require the relaxing of security or impact on other systems.
- Internal staff are not expected or required to fully understand the requirements of this Standard but the emphasis is on them to make sure that software suppliers indicate their understanding and acceptance of the Standard. If any clarification is required, this should be discussed with I.T.
- All IT software, hardware and services should be approved by I.T. or a group containing a senior ICT employee prior to purchase with appropriate consultation for Legal and Security matters (for example, correct use of data or data security).
- Timescales for the installation of software, hardware or systems should be agreed in advance with I.T.
- I.T. should be engaged as early as possible when considering the purchase of new software or systems.
- Business cases should be created and approved for new software.
- Proper contractual arrangements for software support should be considered.
- The supplier will need to sign a Data Transfer Agreement or equivalent if data is required to be transferred to the supplier as part of installation or for support purposes.
- Any support personnel will be required to sign up to the Councils Security Policy (and associated sub policies) that govern conduct and procedures as part of providing remote access support for their software on council systems where appropriate. It is also expected that the suppliers support personnel have undergone a Baseline Personnel Security Standard check.
- Ensure there is appropriate provision for access controls within the system. For example, there should as a minimum be a distinction between an administrator user and a normal user.
- A guarantee should be sought from the supplier of any internally hosted software that they do not have a higher level of access to the system that that of the system administrators.
- Consideration should be given to the ICT Password Policy and ICT Password Standards and relevant aspects should be agreed with the supplier.
- Freeware, shareware, and open source products will be considered for use based on suitability and risk.
- Licensing restrictions on free products must be checked to check suitability in a corporate environment and to ensure installation is not limited to personal use.
- Suppliers must declare any use of additional 3rd party software (Freeware, shareware, and open source products) that is used in addition to their own provided software.
- The Data Protection Officer must be informed if any proposed software or system involves the processing of personal data.
- If a system is hosted external to the Council’s data environment then it must also be compliant with the Council’s Hosted Service Policy and Hosted Service Standards. The sections in this standards document relating to pc software and web front end are still valid.
- Project Management should be considered depending on the Size, complexity and Integration of the system
- ‘Larger’/‘Key’ implementation should have Post Implementation Reviews
- All Council based data needs to be stored on a server at the Central Offices.
- All server components must be installed on the central servers and not on a local pc
- Servers are mainly Windows servers with the occasional exception made for the use of Linux
- Servers are mainly virtualised with some rack mounted physical servers.
- The database preference is Microsoft SQL Server or MySQL/MariaDB but others may be considered at the discretion of I.T.
- Unlike PC installations, any server side installation/configuration can be carried out manually.
- Any communication with the server from outside the internal network must be carried out in a secure manner with appropriate encryption and security controls.
- Any firewall changes required should be clearly stated and documented.
- Any server software must be configured and patched to a level of acceptable risk when assessed using industry standard vulnerability scans, both externally and internally.
- Software is not installed directly onto PCs within the Council, but is remotely distributed centrally by Active Directory Group Policies or SCCM. This means there is a requirement for all software to be an msi or exe installation capable of running silently. This can be achieved in 4 ways and assistance from the software supplier would be expected (if required) in getting one of these methods to work:
- The software comes as a msi or exe that needs no questions answering, so can be distributed "as is" with a silent switch.
- The software comes as an msi, but needs questions answering as part of the install. In this case we would create an mst transforms file to apply against the msi at deployment that would make the msi capable of running silently.
- The software come sas an exe that can be run silently with all options specified as parameters.
- The software comes as a non-msi installation, either as a setup.exe without parameters or as a manual process of copying files onto the pc etc. In this case there would be a need to convert the installation to an msi one. To achieve this, the software installation is "captured" on a test PC using specialised Council software.
- Any prerequisite software, Visual Basic Runtime for example, should be:
- clearly stated
- deployable
- specific versions should be stated
- upgradable to latest secure versions
- Installation and training should not be on the same day, as the preparation and testing for deployment could take more than a day.
- All users have minimum “rights” on the PC (not administrator rights). If modification is required to allow access to certain registry keys or folders, these changes would be added into the “distribution” or modified by scripts/policies. Assistance would be expected, if required, from the supplier to identify these permission changes
- Software should not have Individual licenses for each copy installed, as this makes it impossible to create one distributable copy.
- If plug-in devices are required as part of using the software (e.g. license “dongles”, barcode readers, remote controls etc) then they should be a USB connection that should automatically install on insertion with drivers already added as part of the software distribution, without the requirement for an administrator login. Exception to this requirement is at the discretion of the I.T. section.
- If software can be simply copied to a network drive and run straight from the network drive, the Council would distribute the shortcut to the software via a group policy.
- Printing should be to standard windows networked printers and not, for example, USB unless clearly identified in the prerequisites.
- Each piece of PC software should be standardised on one version to minimise problems with usage across the Authority and software patching.
If access to a system is via a web browser, either to an external/hosted website or to an internal website hosted on one of the Councils servers, then the following policies come into effect.
- The Council standardises on Microsoft Edge and Google Chrome which are available on all PCs. The exception to this is mobile devices.
- There should not be a requirement to change any security settings to connect to a web service that may put the Councils network at risk.
- Shortcuts to access a Website/Webpage are usually remotely distributed to PCs
- The Council does NOT distribute Java (JRE) as standard to all PCs and any requirement for java must be by the use of free alternatives to that provided by Oracle and be capable of updating to latest secure version.
- ActiveX or any other obsolete technologies must not be used.
- Exceptions to the above procedures are at the discretion of the I.T section who should be contacted to discuss any of the above.
Page last updated 19 November 2026
Page feedback
This form is for feedback on the content of this page.
Please do not use this form to contact us about personal matters, as we cannot respond to requests sent this way. To get in touch, use the contact details or online forms provided on this page.
