Our cyber security products span from our next gen SIEM used in the most secure government and critical infrastructure environments, to automated cyber risk reporting applications for commercial and government organisations of all sizes.
In the UK, the National Cyber Security Centre (NCSC) runs an information assurance scheme called Cyber Essentials. Our blog post series looks at each of the framework’s five controls and offers practical hints and tips on how you can meet the security requirements and obtain Cyber Essentials certification., This week we look at patch management.
This post, the sixth and final post in our Cyber Essentials series, focuses on the Cyber Essentials control “keep your devices and software up to date”. Posts 1-5 can be viewed via these links: Post 1, Post 2, Post 3, Post 4 and Post 5. Patch management, applying the latest vendor patches, is one of the most crucial security hygiene activities organisations use to keep their systems protected from viruses and hacking.
If a known vulnerability can be exploited by a hacker to gain access to a computer or bypass security to access information, it’s almost certain that it will be. When a new vulnerability is discovered, a race begins between vendors and hackers. Vendors are trying to fix the problem, which results in a patch being issued, while hackers develop exploits, which are applications that leverage the vulnerability to gain an advantage over the target system. Most of the time, if the security research marketplace is working as it should, when a vulnerability is discovered, it is commonly reported to the vendor well before it’s made public, to give the vendor time to manufacture and test the patch. Once the patch is ready, the researchers release details of their discovery, and point to the vendor patch as the way to address the problem. No situation is perfect, however, and plans often don’t work out.
Microsoft and Apple have robust patch management built into both desktop and server operating systems. Windows 10 also offers several options for keeping devices up to date, and they have extended patching to most of their software application suites too, hence why Office frequently suggests there is an update requiring an installation.
Updates can be applied automatically, which is a great way to ensure you stay current and vulnerabilities are addressed as soon as the fix is available. However, some IT managers switch off auto-update because it’s been known in the past to cause outages, hence the service management team want to first test all updates prior to rolling them out to the business. On the surface of things, this is a good approach, yet it doesn’t consider the risks of delay.
The number of days a system remains at risk when a critical patch has not been applied is a decent measurement of how exposed your organisation is. Each day that passes, the likelihood of the systems being compromised goes up. If you normally apply patches on a monthly cycle, even when critical patches come out, every computer you own will have up to 30 days of exposure. The question you need to answer as a business owner is, is this exposure to ransomware, data theft, denial of service, or critical system compromise greater than the risks relating to rolling out the patch as soon as it’s released? A 30-day patch cycle is really an overt statement of risk tolerance, with specific cost and business value ramifications, tied to the business impact of a compromise compared to the impact of some system downtime (based on a failed installation).
We’ve all heard the term ‘sweat the asset’, which means try to get as much life out of a computer system as possible and don’t upgrade before necessary. Yet the advice from Cyber Essentials points out that, “When the manufacturer no longer supports your hardware or software and new updates cease to appear, you should consider a modern replacement.” Again, this is a risk management exercise, since the longer a system has no official support from the vendor, the more likely the discovery of a vulnerability that never gets a vendor patch.
As a component of your IT strategy, you should have a management plan for equipment obsolescence, which includes upgrading PCs, laptops, mobile devices, servers and network equipment when vendor support ends. Furthermore, managed obsolescence should include software, since software manufacturers also use retiring of support to get customers to upgrade to the latest version.
Asset management is the primary process managed obsolescence falls within, since assets have a lifespan and budgets should be assigned based on those lifespans, thus you are always forecasting when the next ICT spending activity is required for upgrade and replacements (thus, no surprises for the board).
In larger organisations, there are several discrete roles within the business that should be included in the vulnerability and patch management plan. In smaller organisations, the roles still exist, but may be consolidated and managed by one team. Nevertheless, the following list shows the stakeholders that should be included in patch management planning, so the right people in the business can support the process:
The service desk handles user interactions and may need to issue downtime notices to users when a reboot or other business interruption occurs. IT operations usually deploy patches, while the engineering teams would assess their impact on their production systems and look at how the updates would work. Patch assessment (vulnerability management) is a crucial aspect of this process, since their role is to assess the patch implications for their business. Not all critical patches issued by a vendor will require a critical patch response from the business. For example, a critical patch for an operating system feature you don’t use does not require an immediate response, if that feature is disabled.
The ideal situation is that you patch everything as soon as fixes are available. The problem with this is that you may not know a patch is available, especially if the software vendor doesn’t proactively notify customers. It pays to have a catch-all patch management process set up within your service management team to check the vendor websites to see if any new patches have been released. Many platforms don’t have auto-update capability, consequently this manual process becomes even more important.
As cyber risks increase, organisations are encountering the longer life cycle of insurance renewals and the need to demonstrate better management of security controls and their effectiveness.Read more
Highlights and insights from the recent Managed Services Summit in London & the ISACA Central Chapter Conference on Digital Trust, in Birmingham, UK. With two recent conferences in the space of three days, some interesting challenges were very evident in the topics discussed. Being very different events, the challenges were quite different, but interestingly they […]Read more
In early August 2023, the latest joint advisory on persistent vulnerabilities was issued by the intelligence and security agencies of the “Five-eyes” community. These joint advisories are becoming more common. Perhaps recognising the growing importance of shared security information and the common nature of many of the threats faced – the weight they carry makes […]Read more
The quality of your risk assessment and the security information it provides is important; if you plan to use it to actively manage your operational and cyber resilience activities. Organisations are constantly exposed to a rapidly changing threat environment, so you really need a similarly rapid evidence-based feedback system that informs you of the ongoing […]Read more
The UK market has its own regulators, security standards and challenges. And while rulings from SEC in the US or the Australian Prudential Regulation Authority (APRA) in Australia don’t apply to UK companies, for the most part, the observations are undoubtedly relevant and the resulting advice instructive. It would be wrong to think UK financial […]Read more
<<< Part 2a: Australia’s Essential Eight: Beyond Endpoint Control <<< Part 2b: Activating UK NCSC & US NIST Guidelines: Beyond Endpoint Control Part 4: Systematic Measurement of Cyber Controls >>> As much as we invest into cyber security controls, external threats are inevitable. In a recent Notifiable Data Breaches Report from the Office of the […]Read more
Keen campers, scouts and even the Swiss Army know – that a good penknife is indispensable. This simple device has mitigated many a disaster at one point in time or another. Whether it’s to cut through a bit of string, tighten a screw or simply to solve the problem of no bottle opener in the […]Read more
Supply chain risk is an area of cyber security that demands the ongoing attention of every enterprise; because it can make the difference between being resilient or not. It’s no surprise that insurers warn that the vulnerability of supply chains is potentially a systemic risk that can quickly propagate across supply chain dominated industries. Organisations […]Read more
It took a “tripartite cyber assessment” by the Australian Prudential Regulation Authority (APRA) to identify that a sample of financial organisations had inadequate cyber security: poor security control management, a lack of business recovery planning and inadequate 3rd party risk assessment. Why were there gaps? Where is the failure? Clearly the common practice of unsubstantiated […]Read more
The discussion over data-driven vs qualitative cyber security assessment has been going for some time. Nowadays, it is at the top of the priority list for many security and senior executive teams. Managing cyber security has always been a noble ambition but without reliable measurement, the lack of actionable information makes evidence-based management decisions almost […]Read more
Read by directors, executives, and security professionals globally, operating in the most complex of security environments.