Local admin is granted via the Appian form located here:
https://bpi.unisa.edu.au/suite/sites/privileged-access-request
Local admin requests consist of several sections:
Section 1 - Details:
- Contact phone number
- Blueplate
- Local admin requests are always a single-party transaction.
This means that the blueplate that is entered into the request is the sole machine that you will be granted access to.
If you require additional machines, additional requests must be raised and justified accordingly.
- End Date for Access
- Local admin will only be valid for a maximum of 12 months.
Before the 12 months expires, you will be notified to resubmit a justification for your access.
This will then be reviewed and your access will either be removed, or retained.
Section 2 - Business case:
A business case justification relates to the justification you have for requiring local admin access.
The justification must include:
- Business impacts to UniSA for this access not being granted (ie. Inability to deliver course content to students)
- A description of your role within the organisation and how privileged access lends itself to this role.
- The justification must relate directly to the person writing the request. Justifications that are plagiarised or are written collectively will not be approved.
- If applications are being installed that are presently unknown, specify which genre of applications you are most likely to need to install.
We understand that you may not know all applications that will come up, but there is an element of trust from ISTS that you will use privileged access only for tasks related to the justification you have provided.
- The business case justification must ultimately provide a strong rationale, and should objectively make sense without any other context.
Requests that do not meet the above requirements are likely to be declined by ISTS.
Section 3 - Justification:
The request must include all known applications and the estimated number of weekly escalations they require.
This should be truthful and serve to represent why elevated privileges are required.
If you are only elevating privileges once a week for a single application, this would not be representative of a reasonable request.
Additionally, ITHD can connect to your machine and provide access as needed - there must be a justification as to why this is not a reasonable alternative to elevated privileges.
Section 4 - Endorsements:
You must select a line manager to endorse this request.
This will be your direct manager, or anyone above that person in the management hierarchy of your business unit.
Section 5 - Terms and Conditions:
Terms and conditions are provided and must be read and accepted.
If these terms are accepted and subsequently breached, it is considered a breach of the Acceptable Use Policy.
Section 6 - Review:
This provides an opportunity to review your submission before it reaches your manager for approval, and ISTS for subsequent approvals.