Common use of Secure Configuration Clause in Contracts

Secure Configuration. 4.1. An inventory will be kept of all IT hardware and software currently in use at the school, including mobile phones and other personal devices provided by the school. This will be stored in the SBM office and will be audited on a termly basis to ensure it is up-to-date. 4.2. Any changes to the IT hardware or software will be documented using the inventory, and will be authorised by the ICT technician before use. 4.3. All systems will be audited on a termly basis to ensure the software is up-to- date. Any new versions of software or new security patches will be added to systems, ensuring that they do not affect network security, and will be recorded on the inventory. 4.4. Any software that is out-of-date or reaches ‘end of life’ will be removed from systems, i.e. when suppliers end their support for outdated products, such that any security issues will not be rectified by suppliers. 4.5. All hardware, software and operating systems will require passwords for individual users before use. Passwords will be changed on a termly basis to prevent access to facilities which could compromise network security. 4.6. The school believes that locking down hardware, such as through strong passwords, is an effective way to prevent access to facilities by unauthorised users. This is detailed in section 6 of this policy.