- Professional Risks Insurance
- Private Clients
- Farms & Estates
- Commercial Clients
- Wholesale Insurance Broking
- Claims
- About
- Contact
- Log in
26.10.26
A zero-day vulnerability is a security flaw in a technology’s software, hardware or firmware that the product vendor either hasn’t discovered or hasn’t yet patched. Because there’s no fix for this flaw, there’s also no way to prepare for or defend against it. A zero-day vulnerability may go undetected or otherwise unresolved for an extended period, quietly existing within an organisation’s broader IT infrastructure without affecting typical operations.
However, in the hands of cyber-criminals, this flaw could serve as an attack vector, easily weaponised by harmful code or other sophisticated techniques, also called zero-day exploits, to launch a range of malicious schemes at a moment’s notice, including data breaches and ransomware incidents. In these circumstances, an organisation would have no time to protect itself against the impending incident, known as a zero-day attack, making recovery efforts increasingly difficult and compounding total losses until the product vendor is able to develop and distribute a patch for the initial flaw.
Although zero-day attacks can be difficult to combat, there are some steps organisations can take to minimise their exposure. This article provides more information on how zero-day attacks unfold, their potential ramifications and related risk mitigation strategies.

While they may vary based on the type of technology and security flaws involved, zero-day attacks generally follow this sequence:
Discovery – At this stage, a software, hardware or firmware flaw is detected by a cyber-criminal before the product vendor has become aware of or had a chance to remedy it with a patch.
Exploitation – Upon discovering the security flaw, the cyber-criminal exploits this vulnerability, using it to obtain unauthorised access to an organisation’s larger IT environment, escalate privileges, compromise sensitive data and deploy malware.
Identification and response – Once the attack has been identified and the source is tied to the underlying security flaw, the product vendor will investigate the vulnerability and create a patch to fix it. From there, the vendor will release a security update to address the flaw, allowing the impacted organisation to eliminate the vulnerability and proceed with recovery efforts.
During a zero-day attack, an organisation remains at risk until it implements the recommended patch from the product vendor. In some cases, the vendor may promote an alternative mitigation technique rather than a patch to help speed up the affected organisation’s recovery and curb related losses. The vendor may also suggest some temporary configuration changes and briefly disable certain technology features and functions as an extra layer of protection.
As cyber-criminals continue to develop more sophisticated techniques, zero-day attacks have become a rising threat, often targeting enterprise software, networking equipment, operating systems and cloud-based technology to compromise many organisations at once. Nation-state actors and financially motivated cyber-criminals are the most common perpetrators of zero-day attacks, namely, to steal valuable data, deploy ransomware and conduct similar extortion schemes.
Because traditional antivirus programmes and threat detection tools scan for known indicators, they are unlikely to detect zero-day vulnerabilities prior to an attack. Making matters worse, cyber-criminals don’t always make themselves known immediately upon exploiting these security flaws, silently infiltrating an organisation’s systems and processes for days, weeks or even months before being detected. In many cases, such exploitation is only discovered amid incident response and forensic investigation protocols.
Even organisations with mature defence mechanisms and advanced patch management systems in place are unable to remedy security flaws before a fix exists, making it nearly impossible to eliminate zero-day risks. When these attacks occur, organisations may face prolonged operational disruptions, damaged systems and data, large-scale financial losses and lasting reputational decline, especially when the product vendor takes an extended period to develop and distribute an appropriate patch. The longer cyber-criminals evade detection during these attacks, the more time they have to establish further attack avenues for future incidents, paving the way for ongoing disruptions and losses.
Zero-day attacks are not preventable; the best approach that organisations can take to protect themselves is to reduce the likelihood of compromise, limit the potential for damage and ensure prompt recovery processes. Here are some best practices to consider:
Adjust patch management measures. Not all patches are created equal. Some are designed to address larger security flaws and related threats than others. As such, organisations should prioritise their patch management measures based on exploitability and overall business risks.
Keep an accurate technology inventory. To understand the full scope of their zero-day risks, organisations should maintain a well-documented, detailed inventory of all software, hardware and firmware across their IT landscape. Doing so can make it easier to identify and recover vulnerable systems and assets when potential incidents arise.
Implement strict access controls. By upholding the principle of least privilege and segmenting critical workplace networks, organisations can limit lateral movement during zero-day attacks and stop cyber-criminals from causing widespread damage.
Utilise advanced detection and response tools. Organisations should invest in endpoint detection and response (EDR) and extended detection and response (XDR) tools whenever possible. Rather than scanning only for known indicators, EDR and XDR solutions can also identify other suspicious activity, regardless of the exploit signature. This can help organisations detect zero-day attacks faster and prevent cyber-criminals from remaining hidden for extended periods.
Have a plan. Cyber-incident response plans can help organisations ensure that necessary procedures are taken when attacks occur, thereby minimising related losses. These plans should be clearly documented, regularly tested and address a range of scenarios. As it pertains to zero-day attacks, these plans should account for emergency patching, temporary mitigations and expedited change management during active events.
Ensure proper coverage. Finally, organisations should have a robust insurance portfolio to maintain ample financial protection for losses stemming from zero-day attacks. Depending on the nature of the incident and policy wording, cyber insurance may respond to various zero-day losses, including incident response costs, business interruption expenses and liability claims.
Ensure proper coverage. Finally, organisations should have a robust insurance portfolio to maintain ample financial protection for losses stemming from zero-day attacks. Depending on the nature of the incident and policy wording, cyber insurance may respond to various zero-day losses, including incident response costs, business interruption expenses and liability claims.
Organisations that develop or sell technology products may also benefit from professional indemnity insurance.
Zero-day attacks can’t be stopped, but they can be managed. Organisations must focus on reducing their exposure with layered security controls. Pairing these defences with a tested incident response plan and comprehensive coverage can ensure better recovery outcomes when attacks occur.
Contact us today for more cyber-security guidance.
Information provided by Zywave with a contribution from Lisa Langley, Cert CII, Team Leader, Professional Risks, Cox Mahon Ltd.
Complete the details below and we will contact shortly.
This Cyber Risks & Liabilities document is not intended to be exhaustive nor should any discussion or opinions be construed as legal advice. Readers should contact a legal or insurance professional for appropriate advice. Contains public sector information published by the ICO and licensed under the Open Government Licence v3.0. © 2026 Zywave, Inc. All rights reserved.