Your own dedicated server, your own patch clock
ASD sets patch deadlines for a server's firmware, drivers, operating system and applications. Read up the stack to see which of those deadlines sit with you, and which to ask your provider to set out in writing.
General information, not legal or security advice.
Reading the stack
Every figure in the stack is ASD's. ASD's Information Security Manual applies one short clock across the layers: 48 hours from release for firmware, drivers, the operating system of an internet-facing server, and online services, when the vulnerability is assessed as critical by the vendor or when a working exploit exists. When the vendor assesses the vulnerability as non-critical and no working exploit exists, the clock is longer: two weeks for an internet-facing operating system and for online services, and one month for drivers. Other applications have one clock only: one month. ASD's patching guidance gives an example of the pace: once a vulnerability in an online service is made public, malicious code can be expected within 48 hours, sometimes within 24.
Patch times: ASD, Information Security Manual, Guidelines for system management, September 2026 and ASD, Patching applications and operating systems.
The figures are set as type, not drawn as bars, because a month is not a fixed number of days and a bar would assert a length the manual never sets. Read each one as ASD's guidance for organisations. There is no requirement to have an Essential Eight implementation certified by an independent party, though a government directive or policy, a regulator, or a contract may require it to be assessed. If one of those applies to you, check what it asks for.
The column headed Whose reads from ASD's shared responsibility model. The floor is the provider's: the underlying infrastructure, and the third parties involved in providing it, sit with the provider. Above the floor the split is finer. ASD's list of your own responsibilities opens with "Generally, your responsibilities include:", and carries your data, your devices, who gets access, the software you bring and incident response. Four more duties depend on the service you buy: strong authentication, configuration including logging, backups, and the credentials and secrets. And three duties hold whatever the service: the services meet your security needs, you configure them securely, and you decide which data you store in them. Where this site cannot say who holds a layer, it hatches the layer instead, because ASD's own warning is that responsibilities often overlap and that an unclear split leaves gaps in security. The hatch is a question your provider's document has to answer.
Before you rent
These are the questions ASD lists for a customer to ask a provider. CSP, in ASD's wording, means a cloud service provider; on this site, read it as your hosting provider.
Backups
- Does the CSP back up your data or do you need to?
- Are backups automatic and free, or do you need to set them up and pay extra?
- Do backups occur often enough, and can you control their frequency?
- Do backups include all of your important data, and can you control what is included?
- Are backups protected from being accessed, changed or deleted without your approval?
- Do you need to store a copy of the backups elsewhere, and will that cost you extra?
Restoring data
- Can you restore data yourself, or do you need help from the CSP?
- Can you restore earlier versions of your data or only the latest version?
- Have you tested restoring data from a backup?
Incident detection and response
- Does the CSP send you other security alerts that might indicate an incident, and does that cost extra?
- Does the CSP make adequate logs available by default and at no additional cost, to assist you or your chosen third party to perform security monitoring and incident response?
- Do you know how to contact the CSP to ask for help?
- How much help would the CSP provide, and do you have to pay extra?
The OAIC's guidance adds the other side of those questions: where you store personal information with a provider and keep holding it, the reasonable steps it expects can include effective contractual clauses, verifying the provider's security claims through inspections, and regular reporting and monitoring.
One duty runs the other way. Where an external data service provider stores or processes business critical data for a critical infrastructure asset, the entity must notify that provider, so the provider knows it may carry obligations of its own under the Security of Critical Infrastructure Act 2018.
Where these come from
The clocks are ASD's Information Security Manual, Guidelines for system management, September 2026, and the practice behind them is ASD's Patching applications and operating systems. The split of duties is ASD's shared responsibility model, in its guidance for individuals and small and medium businesses and its Executive guidance; the always list is from Cloud computing security for executives; and the maturity levels are from the Essential Eight maturity model. The privacy guidance is the OAIC's, and the reporting guidance is the Cyber and Infrastructure Security Centre's. The Acts and the rules the guides name, the Privacy Act 1988 among them, sit on the Federal Register of Legislation.