Multi-factor authentication: the practical NZ business guide
The best MFA rollout is one staff can complete without leaving gaps attackers can exploit. For a small New Zealand business, that means protecting the accounts that matter most, checking how people actually work and planning for lost phones before making MFA compulsory.
Start with an account inventory, not an enrolment email. Include Microsoft 365 or Google Workspace, payroll, accounting, banking, cloud storage, remote access, domain registration and backup administration. Record the system owner, users, available MFA methods and recovery process. Your IT provider should identify older applications and connections that cannot meet the intended policy.
Nominate a business sponsor who can resolve access and device decisions, plus a technical owner responsible for configuration and testing. Choose a rollout window that avoids payroll processing, GST filing deadlines and peak trading. Define success as enforced protection across the agreed scope, not simply the number of people who have registered an authenticator.
Choose factors that resist phishing, not just passwords
MFA combines different types of evidence, such as a password and possession of a registered device. Two passwords do not count. Methods differ significantly: a code can be stolen through a convincing fake sign-in page, while phishing-resistant authentication binds the sign-in to the legitimate service.
Where supported, prefer FIDO2 security keys or passkeys configured to require local user verification, such as a PIN or biometric. Confirm that your applications and identity policies support the chosen implementation. For administrators and people authorising payments, prioritise phishing-resistant methods rather than treating every factor as interchangeable.
- Security keys suit privileged users and staff without suitable phones. Register a spare and store it securely; check compatibility with shared workstations and mobile devices.
- Passkeys can simplify sign-in. Decide whether device-bound or synchronised credentials fit your device-management and recovery requirements.
- Authenticator apps are a practical fallback. Prefer number matching over simple approve-or-deny prompts, while recognising that number matching is not phishing-resistant.
- SMS is better than password-only access where nothing stronger is available, but carries SIM-swap, coverage and interception risks. Avoid making it the default for privileged accounts.
Roll out in stages, with clear completion gates
A staged rollout limits disruption, but should not become months of optional enrolment. Give each stage an owner, a deadline and a test that proves MFA is actually enforced. If your platform offers report-only policies, use them to find likely failures before switching enforcement on.
Check licensing and application support before promising controls. A service appearing behind single sign-on may still allow direct password access; test that route too.
- Pilot with a small mixed group: an administrator, an office worker, a remote worker and someone using a shared device. Test ordinary work, mobile access and recovery.
- Protect privileged accounts first after the pilot. Use separate administrator and everyday accounts, and cover backup consoles, security tools and domain management.
- Enforce MFA for business email, your central identity platform and remote access. Email is especially important because it often receives password-reset messages.
- Extend enforcement to finance systems and remaining applications. Confirm that staff cannot bypass the policy through an alternative sign-in method.
- Identify and disable legacy authentication that cannot satisfy MFA, after checking dependencies such as scanners or older mail clients. Replace affected workflows rather than leaving broad bypasses.
Make enrolment and recovery part of the rollout
Tell staff what is changing, when it becomes compulsory and where to get help. Explain that an MFA prompt should correspond to a sign-in they have just initiated. Provide enrolment instructions through a known internal channel so a surprise email asking people to scan a QR code does not become the model for future phishing.
Set aside supported enrolment time during working hours. Test access to the actual applications people use, not just the identity portal. Where supported, register a second approved method, and explain how to replace a phone before wiping or trading in the old one.
Do not assume everyone can or will use a personal phone. Offer a business-funded alternative, such as a security key, and explain what an authenticator app does and what the employer can see.
Recovery is another authentication route, so protect it accordingly. Require documented identity checks before resetting factors; caller ID or an email from the affected account is not sufficient. Notify the user through a trusted channel when authentication methods change.
Handle exceptions without creating permanent holes
Some systems will not support your preferred method. Keep an exception register recording the account, business reason, risk, compensating controls, approver and expiry date. Review it regularly. An exception without a replacement plan usually becomes a permanent weakness.
Distinguish human users from automated workloads. A script cannot reliably respond to an MFA prompt; use supported workload identities, managed identities or certificate-based authentication instead, with tightly scoped permissions and monitored credential lifecycles.
- For shared mailboxes, prefer delegated access through named user accounts with MFA. Avoid distributing one password and one shared authenticator.
- For contractors, assign named accounts, an internal sponsor and an access end date. Confirm how MFA will be enforced before granting access.
- For older applications, restrict network access and privileges while arranging an upgrade or replacement. Compensating controls reduce risk; they do not make the application MFA-protected.
- For emergency access, follow your platform's documented approach. Minimise dependence on the normal sign-in path, protect credentials securely, alert on every use and test under controlled conditions.
Teach staff how to stop MFA fatigue attacks
MFA fatigue attacks bombard someone with approval requests until they accept one, sometimes followed by a call from a supposed technician. Simple push approval makes this easier. Number matching reduces accidental approvals, but an attacker can still coach someone through a fraudulent sign-in.
Give staff one clear rule: do not approve, enter or relay authentication information for a sign-in you did not initiate. A person claiming to be IT must not persuade them to approve a prompt to stop the notifications.
Specify an after-hours reporting route. An urgent approval mistake should not sit unattended in an inbox until Monday.
- Deny unexpected prompts and report them immediately through a known help desk number or reporting channel. Do not use contact details supplied by the caller.
- If an approval was accidental, say so promptly. Treat this as a possible account compromise, not a training failure to hide.
- Have IT investigate sign-in records, revoke active sessions where appropriate, reset compromised credentials and check registered factors, mailbox rules and other account changes.
Verify coverage and keep it working
After rollout, ask for evidence of enforcement, not just registration. Review accounts outside policy scope, unused accounts, weak fallback methods, unexpected factor changes and applications still permitting password-only access. Test new-starter, leaver and lost-device procedures.
Review exceptions and privileged access regularly, and repeat checks when adding applications or changing providers. MFA reduces account takeover risk, but it does not replace device security, monitoring or independent verification of payment changes.
CorTech can help Auckland and wider New Zealand businesses plan and manage this work through project management, help desk support and its 24/7 NOC and SOC. Agree who monitors authentication alerts, who can contain a compromised account and who the business should call when access fails.
Want this handled for you?
CorTech provides 24/7 monitoring, security operations and help desk support for businesses across Auckland and New Zealand.