COI Report –
Part VIIPage
385 of
425 47.1.5 Upgrade timelines 1122. The general (unwritten) policy of upgrading software at EOL should be reviewed. IHiS’ approach was to consider factors like cost,
user needs, proximity to EOL, and compatibility with existing environment, when deciding whether to upgrade software. Security was not one of the main considerations. This strategy may have been acceptable six or seven years ago. It is not today. This approach emphasises cost and
operational ease over defence, and is at best nave in the current cybersecurity environment.
1123. The longer apiece of software has been released, the longer malicious actors and security researchers will have to find vulnerabilities that can be exploited. Often, the exploitable entry points for commercial software are made public by researchers so that users can be made aware, and so that software companies can take steps to fix them. Software companies then release anew version of their software to address these security issues. Many cybercriminals track information about vulnerabilities. Once
they find anew vulnerability, the criminals work as quickly as possible to develop an exploit to abuse the vulnerability. Using such an exploit, hackers can then target victims who have yet to update their software.
1124. Ideally, all information technology software applications should generally reflect the most recent version of the application software that is properly vendor- supported. Where this is not possible,
as a rule of thumb, the installed version of the software should be no more than two versions behind the most recent commercially available version. This is because the longer software goes without upgrades, the longer the list of accumulated exploits to which it maybe vulnerable.
1125. Separately, Vivek testified that recent years have seen software evolving with an increased focus on the escalating
cybersecurity threats, and versions released recently are far more secure than those deployed eight, nine or ten years ago, when the constant threat did not exist.