Who these recommendations are for
We address them to the IT administrator responsible for the security settings of the installation, and to the OHS manager who assesses the impact of logins on shift work. Both roles should agree on the settings before MFA goes live, because the effects are seen first on the floor: longer logins, a blocked account, a helpdesk call in the middle of a shift.
Recommendation 1: enable MFA deliberately, per installation
Multi-factor authentication is a security setting enabled per installation and off by default. This is good news for planning: you can roll it out in stages. Start with administrative accounts and accounts with access to personal data, and only after a few weeks extend it to the rest.
Before enabling it, agree with the OHS manager on a list of roles for which login must be quick, for example a dispatcher during an incident. For them, plan the TOTP app, because it works without e-mail and does not depend on message delays.
Parameters of multi-factor login
Recommendation 2: choose the right factor for each role
The system offers two factors: a six-digit code sent by e-mail, valid for 10 minutes with a limit of 5 attempts, and TOTP compatible with popular authenticator apps. The e-mail code is convenient for office staff with e-mail access. TOTP works better for people who work in areas without e-mail access or with network delays.
The limit of 5 attempts protects against guessing the code, but it also means that an employee who makes several mistakes needs a new code. Tell the helpdesk about this rule so it does not treat every lock as a failure.
Recommendation 3: set trusted devices with care
A trusted device remembers the verification for 7 days through a cookie. For a workstation assigned to one person this is a sensible setting, because it limits codes to one per week. For a shared computer in the dispatch room it is a risk, so such workstations should use a shorter memory or a login without remembering the device.
- Personal workstation: remember for 7 days.
- Shared workstation: do not remember the device.
- After a password change or loss of a phone: force verification again.
Recommendation 4: turn off the code requirement for kiosk devices
A watch without a keyboard and a kiosk cannot type a code. Such devices use a separate kiosk account flag, which is switched on explicitly for named accounts. Make sure device accounts are separate, named after the device and covered by log monitoring, rather than shared across the whole fleet.
We described this in the case of a watch that went silent after its token expired. The compensating rule for such accounts is to limit permissions to what is necessary and to review warning entries.
Recommendation 5: know the token lifetimes
API and mobile applications use JWT tokens, and the browser uses a session. The access token is valid for 12 hours and the refresh token for 7 days, and it is single-use. For planning, this means that an employee who logs in once per 8-hour shift will usually not see a request to log in again during the day, but after 7 days of inactivity they certainly will.
Recommendations 6 and 7: the fallback path and communication
Describe the procedure for regaining access for a person who has no phone and no e-mail. It should include identity verification by a supervisor, an entry in the change register and a limited validity period for the workaround. Without such a procedure, the helpdesk improvises it under pressure.
Before enabling MFA, send employees a short instruction with three scenarios: first login, loss of phone, code does not arrive. The last scenario concerns e-mail, so direct recipients to the description of the system's sending mail if messages land in quarantine.
Video
Frequently asked questions
Is MFA enabled by default?
No. It is a security setting enabled per installation and off by default, so the rollout can be spread over stages.
What about devices without a keyboard?
They use a separate kiosk account flag that is switched on explicitly. IT names the accounts, and their use is visible in the log.
How many attempts does a user have to enter a code?
Five. The e-mail code is valid for 10 minutes, and after the limit is exceeded a new code must be generated.
Let's plan MFA together with IT and OHS
We will agree on roles, factors and exceptions for kiosk devices before the first employee sees a request for a code.
Let's talk