A monthly maintenance window can help you plan routine IT work. It should not mean every security update waits until next month. When attackers are exploiting a weakness in a system your business uses, your IT provider needs a way to act sooner.
On 17 November 2026, the Australian Signals Directorate’s Australian Cyber Security Centre, or ACSC, published a warning about unpatched software. It said some vulnerabilities had been successfully exploited within 48 hours of patches or mitigation advice becoming available. Automated and AI-enabled tools are also helping attackers find and exploit weaknesses faster, the ACSC said.
That is not a universal 48-hour deadline, and it does not mean waiting 48 hours is safe. The practical message for small businesses is to prioritise updates by risk, rather than treating the calendar as the only deciding factor.
Which security updates need attention first?
A security update fixes a weakness in software. You might also hear it called a patch. Some weaknesses need a faster response because attackers are already using them, or because the affected system is reachable from the internet.
Ask your IT provider to check:
- Whether the flaw is being exploited. Check the vendor’s advisory and relevant ACSC alerts, rather than relying on a generic update notification.
- Whether your business is affected. Confirm the product, installed version and configuration. An urgent alert for a product you do not use is different from an exposed system you depend on.
- What attackers could access. Give particular attention to systems that provide remote access, administrator access or access to business data.
- What the vendor recommends. Follow the product-specific instructions for patching, temporary protections and any checks for compromise.
Routine work can still have a planned schedule. The gap to avoid is having no process for urgent updates between maintenance windows.
Know who updates each system
The ACSC recommends confirming that suppliers can promptly patch systems they manage on your behalf. Paying for a managed service does not tell you which systems that service covers.
Keep a short list of your business devices, firewall, remote-access tools, website and important applications. For each one, record who manages updates and who you contact about an urgent alert.
For a supplier-managed system, ask:
- Is this product included in our support agreement?
- Who checks security advisories and decides when action is needed?
- How do you handle an urgent update outside the usual maintenance window?
- Who approves downtime, and what happens if that person is unavailable?
- What confirmation will we receive when the work is complete?
If a system no longer receives security updates, ask about replacing it or removing it from use. The ACSC warns that unsupported systems are easy targets.
If you cannot patch immediately, reduce access
Some updates need compatibility checks or planned downtime. The ACSC says that when updates cannot be applied immediately, organisations should assess the risk, restrict exposure and use temporary security controls until remediation is complete.
Your IT provider should choose controls that fit the affected product and its vendor guidance. Depending on the system, that could mean disabling an affected feature, limiting access to approved connections or temporarily taking a vulnerable service offline.
Record what is still exposed, who owns the decision and when the provider will review it. A temporary restriction needs a follow-up plan. It should not become an undocumented reason to leave the system unpatched.

Check the result, not just the update request
Ask your provider to confirm the installed version or patch status on each affected system. An update being approved or scheduled is not proof that it installed. Check for failed devices, offline laptops and any required restarts.
Urgency does not mean installing every update without preparation. Agree on proportionate compatibility testing, recovery steps and a short check of essential business tasks after the change. The checks should match the risk and the vendor’s instructions, without creating an automatic month-long delay.
Where a vendor warns about active exploitation, ask whether it also recommends checking for signs of compromise. Installing an update does not establish that a system was never accessed before the fix.
What to ask your IT provider this week
Ask your IT provider this question:
“If a serious vulnerability affects our business tomorrow, what happens before our next maintenance window?”
You should be able to identify the responsible person, the affected systems, the proposed action and how completion will be checked. Enable automatic updates where appropriate, as the ACSC recommends. Agree which systems need managed testing or downtime.
Need a clearer update plan?
JCPIT’s small-business IT support includes patch oversight for business devices within the agreed service scope. If you are unsure who looks after your updates, talk to JCPIT about your devices, suppliers and support arrangements. We can discuss the gaps and agree what needs attention first.