Guide 1 of 7Hatched: ask
Who looks after a dedicated server, you or the host?
Renting a whole machine splits it between a provider and you. ASD's shared responsibility model says which duties are always yours, which are generally yours, and which depend on the service you buy; the hatched layers of the stack are the ones your provider's own document has to place.
General information, not legal or security advice.
What ASD's split says
ASD's shared responsibility model exists to answer one worry: when a service is rented rather than owned, who does what? It opens with the duty that survives everything else. As the customer you will always have some responsibilities, and you also carry the risk of your data being stolen, changed without your approval, or you losing access to it. That can mean financial loss, reputational damage and legal issues, and ASD is plain that the risk cannot be outsourced to a provider.
The model then sorts the work into three groups. The first list is introduced with "Generally, your responsibilities include:", and it holds five duties:
- your data, meaning control of who can access it, and using services and support staff in countries that suit the sensitivity of the data;
- your devices, meaning only trusted devices reach and manage the service;
- cloud resource access, meaning people get only the access they need, with separate accounts to limit the harm of one being compromised;
- the software you bring, meaning reputable choices, configured securely and patched as soon as patches appear;
- incident response, meaning being ready to act quickly on cyber security alerts.
A second list carries the duties that depend on the service you actually buy. Its lead-in is "Depending on the cloud service you use or plan to use, and if it is securely designed and securely configured by default, your responsibilities might also include:", and it holds four:
- strong authentication, meaning phishing-resistant multi-factor authentication on the accounts that reach the service;
- configuration, including logging, because the default settings may not be secure enough or suitable for your needs;
- backups of data, software and settings; ASD says these might be part of the service, offered as an optional extra, or required of you;
- credentials and secrets, kept managed and short-lived, and never stored in code repositories or configuration files.
A third list is the shortest, and it applies whatever the service: the services meet your security needs, you configure them securely, and you decide which data you store in them. On the other side of the split, the provider holds the floor: the service has to be securely designed, set up and operated, and that includes the underlying infrastructure and every third party involved in providing it. The reason this site draws firmware, drivers and the operating system as hatched, rather than colouring them either way, is ASD's own warning: responsibilities often overlap, and where the customer and the provider are unclear on who is responsible for what, that can leave gaps in security.
The example ASD gives
ASD's example of the arrangement that leaves the most with the customer is a web server and its operating system, managed by hand rather than run for you; the guidance is written to shrink the customer's share, and its recommended move is the other direction, to a trusted hosted service that carries the website instead. An unmanaged dedicated server is closer to the first arrangement than the second: unless the provider's document says otherwise, the operating system and the software you bring are likely to be yours to patch and watch. That is why the guide that follows, on patch deadlines, has so much ground to cover.
One honesty note about the model. ASD wrote it for cloud services, and it is the nearest official split of a rented service's duties there is; ASD also warns, in the same guidance, that a vendor adding the words "cloud" or "as a Service" to the name of a product does not automatically mean the vendor is selling cloud computing services as NIST defines them. Nowhere on this site is a dedicated server called cloud or called infrastructure as a service. Where the model's sentences say cloud, read them as the rented service they describe, and keep the split.
What to ask for in writing
ASD's instruction to customers is direct: use a provider that supplies its shared responsibility documentation, review that documentation for each service you use or plan to use, and if a provider does not supply such documentation, consider choosing a different provider. It also says to ask for the provider's IRAP assessment, and the Executive guidance asks for that assessment including the detailed residual risks. ASD's suggested reading list then starts with the Department of Home Affairs' Hosting Certification Framework. The Executive guidance also asks about location: does the provider guarantee that its services, including its support staff, are located in countries that are suitable for the sensitivity of the data?
This page stops at the band. No official source states where one provider's line falls against another's, so the honest drawing is the band itself: the layers to ask the provider to put in writing, and the questions that make it place them. Ask before the contract, not after the first incident.
Reading the hatched rows
Three words carry the marking column of the stack. Provider is the floor, and the third parties in it, which ASD puts with the provider. Generally yours is ASD's own lead-in for the list of your duties, so every layer marked with it sits on that list. Ask is the hatch, and it means what it says: the layer is one the model leaves to the provider's own responsibility document, so ask for the document and read its answer layer by layer. A hatched layer is not an unknown; it is a question with a written answer somewhere, and the point of the drawing is that the answer belongs in front of you before the contract.
One caveat on the clock figures beside the hatched rows, and above and below them. They are ASD's recommended times for organisations. The Essential Eight needs no certification by an independent party unless a government directive or policy, a regulator, or a contractual arrangement requires it, and the Essential Eight is ASD's summary of the most effective of its mitigation strategies. The times are ASD's recommended practice; a government directive or policy, a regulator, or a contract may also require your implementation to be assessed by an independent party.
The whole stack, bottom to top (dedicated-servers.com.au home)