About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Give each outside technician, whether from your IT partner or an application vendor, a named account limited to the servers they support, with an end date or a booked window, and nothing else. Record every outside account in an access register with who approved it and when it was last reviewed, and review it at least yearly, whenever a technician leaves the partner firm and whenever a partner's or vendor's contract starts, changes or ends.
Why it matters
Depending on the role it is given, a hosting portal account can reach every server the business hosts there. Outside accounts are the ones most easily forgotten: a shared partner login, a vendor account left open after an upgrade, or a former contractor whose access was never removed puts all of it at risk. Because the people behind those accounts work for another firm, the business does not see when they leave, so the access has to end by date or by review, not by someone remembering.
How it works
Two principles
NIST, the United States standards body, defines separation of duty as "the principle that no user should be given enough privileges to misuse the system on their own". It defines least privilege as restricting access "to the minimum necessary to accomplish assigned tasks". For outside access, these mean a partner or vendor technician holds rights only to the servers and actions their task needs, and only for as long as the task lasts.
Australian guidance on administrator rights
The Australian Signals Directorate's Essential Eight treats restricting administrative privileges as one of its eight mitigation strategies. Its maturity model includes these requirements:
- "Requests for privileged access to systems, applications and data repositories are validated when first requested."
- At Maturity Level Two and above: "Privileged access to systems, applications and data repositories is disabled after 12 months unless revalidated."
- Also at Maturity Level Two and above: "Privileged access to systems and applications is disabled after 45 days of inactivity."
In our reading, a hosting portal administrator role is privileged access in this sense. The same model asks that "Privileged users are assigned a dedicated privileged user account to be used solely for duties requiring privileged access."
What to choose and why
Where outside roles sit
This article concerns the outside rows of the table below; the internal rows are shown only for context.
| Person | Portal rights | Notes |
|---|---|---|
| Business owner or director | Approve access; view billing | Approves new administrators |
| Finance | Billing and invoices only | No server control |
| Internal IT administrators | Server control for agreed actions | Own named accounts |
| Outside IT partner | Server control for supported servers only, time-limited | Renewed by approval, not by default |
| Application vendor | Console or remote access to one server, during a booked window | Removed after the work |
| Managers wanting reports | View-only usage and status | No control |
The table is editorial guidance; portal role names and options differ between providers.
Keep an access register
For each portal user, record name, organisation, role, who approved it, when, and the last review date. Review it:
- at least every 12 months (for administrator roles this matches the Essential Eight Maturity Level Two requirement to revalidate privileged access; for other roles it is our recommendation);
- when a staff member leaves or changes role;
- when an outside partner's contract starts, changes or ends.
Ask your provider whether its portal can report users and last sign-in times, so inactive accounts can be found. The register also answers the first question an auditor, insurer or new IT partner is likely to ask: who can change our servers?
Outside IT partners
Give each partner technician their own account rather than a shared partner login, so actions are traceable and one person's departure removes only their access. Ask the partner to tell you when a technician leaves, and check the register against the partner's current staff list at each review. Set an end date on partner access and renew it by approval. When a partner relationship ends, remove all its technicians' accounts on the last day, and change any passwords they may have known for servers or shared services.
Application vendors
A vendor usually needs access for a specific job, such as an upgrade or a support case. Open a named account for the vendor's technician limited to the one server involved, for a booked window, and remove it when the work is done rather than leaving it for the next visit. Record the job, the window and who approved it in the register.
Illustrative example
A 30-person business has an outside IT partner and an accounting-software vendor. The partner's two technicians have named accounts limited to the servers they support, ending with the contract year. When one technician leaves the partner firm, only that account is removed. The vendor's technician gets an account for the accounting server for one evening's upgrade, and it is removed the next morning. The example is illustrative.
Read next
Related articles you may want next.
- HostingYou, your IT partner and the hosting provider: making a three-party arrangement workHow a business that uses both an outside IT partner and a separate hosting provider decides who acts first when something breaks, what access each party needs, and how to write it down so nothing falls between them.Read article
- HostingProvider administrator access in managed hosting: who can log in, how it is logged, and break-glass accountsWhat administrator access a managed hosting provider holds to a customer's servers, what Australian and Microsoft guidance says about controlling and logging privileged access, how emergency break-glass accounts should work, and the questions to ask before signing.Read article
- HostingSelf-service in a hosting portal: which actions to do yourself and which to requestAn action-by-action view of hosting portal controls (restart, power off, console, snapshots, resizing and network changes) showing which are low-risk for a customer administrator and which have consequences that justify a request to the provider.Read article
Risks and limits
- Portals differ. Some offer fine-grained roles; others offer only "administrator" and "viewer". Where roles are coarse, compensate with fewer administrators and more frequent review.
- Portal access is one layer. A partner's or vendor's sign-in rights inside the servers themselves need the same end dates and review.
- The Essential Eight is a benchmark. It is written as guidance; which maturity level suits your business is a decision for you and your advisers.
- Emergency access needs a plan. Decide in advance who acts if every named administrator is unavailable.
Sources
Opened 15 November 2026.
- Australian Signals Directorate: Essential Eight maturity model, web page current at opening; downloadable edition dated November 2023.
- NIST Computer Security Resource Center: Separation of Duty (SOD), glossary.
- NIST Computer Security Resource Center: least privilege, glossary.
Related service: Cloud hosting.
Learning notes
- Give outside partners and vendors only the servers and actions their task needs.
- Essential Eight: validate privileged access when first requested.
- At Maturity Level Two, privileged access is disabled after 12 months unless revalidated, and after 45 days of inactivity.
- Give each outside technician a named account limited to the servers they support, with an end date or booked window.
- Remove a vendor's account when its job is done, and a partner's accounts on the last day of the relationship.
- Keep an access register with approver and last review date.
This article was originally published on .