External user onboarding process
Please note, this process excludes GBPO, and contractor accounts which do not require admin (-adm or -az-adm) accounts and is in relation to IT contractors who may/may not require elevated privileges to our environment.
Pre-checks and tasks
Maddocks staff member to provide onboarding form and forward to COO for approval & Email P&C as an FYI to save details.
The form should be completed and be inclusive that they have a valid police check or higher clearance which has been sighted and documented.
Onboarding the user
Once documentation is cleared, P&C to forward to [email protected]. If it is by the request of Infosec team - P&C should be notified, but aren't required to approve.
Infosec will not be proceeding further unless
these requirements have been met.
These two documents refer to onboarding both a team group and a user. If you require access, please seek approval from Nirav.
- If this user is from a new group who has not previously worked for Maddocks before, please start with this
process.
- If the team group does exist, please proceed with this documentation.
Supplying credentials to the user
Please follow this KB when supplying credentials to the user and ensure Magic Links are treated as confidential.
https://helpdesk.maddocks.com.au/a/solutions/articles/10000090756?language=en
Infosec to set account to expire as outlined within P&C document.
Offboarding
During privileged access reviews move off-boarded users, please advise
P&C if any accounts have been disabled/offboarded.
Full Name |
|
Gender |
|
Company |
|
Mobile Number |
|
Start date |
|
End date (if temp) |
|
Work Type |
|
Maddocks position title* |
|
Maddocks practice team |
|
Training Required |
|
Payroll (Aurion) /Finance (Aderant Expert) access required |
|
Reporting to |
|
Maddocks login and/or laptop required |
|
Access Required |
|
Access pass required |
|
Current Police check on file? |