A new employee's first day is one of the most common sources of credential security failures. In the rush to get someone productive quickly, it is tempting to share a general password, let them reuse their previous company's credentials, or defer security setup to "later in the week." This checklist structures the process to prevent those shortcuts from creating lasting vulnerabilities.
Day-One Security Checklist
- โ Create company email account with generated password (not the employee's name or a default)
- โ Enable MFA on company email, walk the new employee through setup on day one
- โ Invite to company password manager, provide vault and shared collections appropriate to their role
- โ Create individual credentials for each system they need, generated by the manager, not shared verbally
- โ Enrol on any SSO (Single Sign-On) system, test that logins work before end of day
- โ Provision laptop or device with disk encryption enabled and confirmed
- โ Brief on the password policy, 15 minutes, not a document to read later
- โ Confirm emergency contact for account recovery in case of device loss
Who Owns Which Step
One of the most common reasons onboarding security breaks down is that nobody is sure who is responsible for what. When HR, IT and the line manager each assume someone else has covered a task, new starters can end up with the wrong access or no guidance on the rules they are expected to follow.
HR should issue the acceptable use policy before day one, collect the role and start date information IT needs to provision accounts, and flag any changes promptly so access can be adjusted before it is created rather than after.
IT should:
- Create accounts with the minimum permissions required for the role rather than copying a colleague's existing profile.
- Set a temporary password that forces a change on first login.
- Provide clear written instructions for setting up multi-factor authentication before the new starter's first working hour.
The line manager should:
- Confirm which systems the new starter genuinely needs access to, and which they do not.
- Cover password expectations, phishing awareness and how to report an incident on day one.
- Raise a formal access request rather than asking a colleague to share credentials as a short-term workaround.
The First Week After Onboarding
The accounts are live, but the first week is where onboarding security either holds or starts to drift. A short verification routine before the end of the week catches the most common problems before they become habits.
IT should confirm that the new starter has changed their temporary password and enabled multi-factor authentication on every required account. If either step has not been completed, it should be treated as a priority rather than a note for a later follow-up.
The line manager should check in briefly to ask whether the new starter has encountered any requests to share credentials, any unexpected access, or any confusion about what they are and are not permitted to do. These conversations take only a few minutes and often surface small problems early.
Common issues to watch for during the first week include:
- A temporary password still in use because the change process was not explained clearly.
- Inherited access from a previous employee in the same role that was never revoked.
- A colleague sharing their own login to help the new starter get started quickly.
- Multi-factor authentication set up on a personal device where your policy requires a company-managed one.
Most of these can be resolved quickly if caught early. A brief note logged by HR or IT confirming the checks were completed also provides a useful audit trail should a question about access arise later.
What Not to Do
- Do not email a password, even temporarily. Use the password manager's secure sharing
- Do not create an account using a generic name like "[email protected]", accounts must be individual
- Do not skip MFA setup because it "takes too long", the cost of a compromised account far exceeds 15 minutes
- Do not give access to sensitive collections (finance, admin) until role requires it and probation is complete