Nine in Ten Australian Organisations Have Been Burned by Slow Patching, Survey Finds
Research commissioned by enterprise Java provider Azul suggests slow patching is a widespread problem. In a survey of 200 Australian cybersecurity leaders, 90% reported at least one incident, suspected incident or near miss linked to slow patching, and 57% said they had experienced a confirmed incident.
The report points to a growing gap between attacker speed and defender speed. More than half of respondents (51%) believe AI-equipped attackers can develop a working exploit within one to three days of a critical vulnerability being disclosed, and 7% think it can happen in under 24 hours. Meanwhile, 45% said deploying a critical patch across production typically takes four to six days, and 15% said it can take up to a week. Testing before deployment was a major cause of delay: 42% said it adds four to six days to their Java patching cycle, while 30% said it adds one to three weeks.
Process gaps also stood out. Only 33% mandate patching of non-critical vulnerabilities within a defined timeframe, 32% patch on a best-effort basis, and 14% have no formal patching policy. Azul tied the report to an October OpenJDK quarterly update that it said included a record 53 vulnerabilities. A separate survey of 300 US security leaders showed similar themes. Note that these findings come from vendor-commissioned research, and this summary covers only the opening of the original article.