Passwords, Passkeys and Multi-Factor Authentication for Accountants
Remember a strong passphrase and let a firm-approved password manager remember unique passwords for other accounts. Use phishing-resistant sign-in where supported and keep API credentials in a secrets manager.

Xian Hui
9 November 2026 · 7 min read

In brief
How should accountants protect their work accounts and respond to unexpected sign-in prompts?
Remember a strong passphrase. Let your password manager remember the rest. Use random-word passphrases for passwords you must remember and unique generated passwords for other applications. Prefer supported passkeys or security keys, enable MFA and keep API credentials in a secrets manager. Never paste secrets into AI tools or spreadsheets.
What you'll learn
- Choose a passphrase or generated password for the way an account is used
- Apply NIST guidance on password length, composition and changes
- Distinguish user passwords from API keys and machine credentials
- Keep secrets out of AI tools, spreadsheets and shared documents
- Respond safely to unexpected sign-in prompts
Passwords, Passkeys and Multi-Factor Authentication for Accountants
An accountant signs in to cloud accounting software, a document repository and a payroll platform every working day. The accounts may contain different types of client records, but the same weak password must not become a way into all three.
Remember a strong passphrase. Let your password manager remember the rest.
Why is reusing a password risky?
A leaked password can be tried against other services. Never reuse passwords across Xero, Microsoft 365, banking, email or client systems. The Cyber Security Agency of Singapore (CSA) identifies password theft and reuse as significant risks.
Prefer individual accounts with role-based permissions. Shared accounts make it harder to identify who accessed a record.
Should I use a passphrase or a generated password?
A passphrase is several words used together as one password. Pick the words at random and make sure they are unrelated. A long passphrase is generally easier to remember than a complicated string of characters. Avoid common phrases, quotations, names, song lyrics and predictable word combinations. Length and unpredictability matter more than forced uppercase letters, numbers or symbols.
Example: copper lantern drizzle orbit. Do not use this example. It is now public.
| Account or credential | Recommended approach |
|---|---|
| Password manager master password | Long passphrase of randomly selected, unrelated words. |
| Windows account password | Long passphrase if you must remember and type it. Use Windows Hello or a passkey where the firm has set it up. |
| Microsoft 365, Xero, email, banking and other applications | Unique, randomly generated password stored in the password manager, or a passkey where supported. |
| API keys, AI agents and machine credentials | Cryptographically secure random secret stored in a secrets manager. |
These are practical recommendations, not rules requiring passphrases for specific applications. Use a reputable, firm-approved password manager with a long random-word passphrase as its master password, and turn on MFA for the manager. Generate a different password for every account. Staff should not need to remember dozens of complicated passwords.
What does current NIST password guidance require?
The National Institute of Standards and Technology (NIST), SP 800-63B Revision 4, section 3.1.1.2, sets requirements for verifiers, the systems that check passwords. They must:
- Require at least 15 characters for passwords used as the single authentication factor.
- Require at least eight characters for passwords used only as part of MFA.
- Not demand character mixtures, such as uppercase letters, numbers and symbols.
- Not force scheduled password changes, but require a change when there is evidence of compromise.
- Check new passwords against a blocklist of common, expected or compromised passwords.
- Allow password managers and autofill. NIST also recommends allowing paste.
The 15 and eight character thresholds are minimum requirements for passwords a system accepts, not targets. An eight-character password is not secure merely because it meets the MFA minimum. Longer is better.
NIST's public password advice identifies length as the most important feature, recommends at least 15 characters and a password manager, and no longer recommends requiring special characters and numbers.
How does Windows Hello differ from a Windows password?
A Windows account password is a reusable password. A Windows Hello PIN unlocks credentials on one device. Windows Hello biometrics use a face or fingerprint for that local unlock. A passkey is a service-specific cryptographic credential, distinct from its unlocking PIN or biometric gesture.
Microsoft's Windows Hello for Business overview explains that the PIN stays on the device, credentials use its TPM security module for protection and biometric data stays local. There is no shared password to steal from a server or phish and use remotely.
A short Hello PIN therefore carries different risks from a short reusable password. Use firm-configured passwordless sign-in where supported. You do not need a passphrase for that sign-in.
Are API keys and AI agent credentials passwords?
API keys are not user passwords. Generate secrets with a cryptographically secure random generator. OWASP requires secure, cryptographically robust generation, minimum necessary privileges and revocation of potentially compromised secrets.
Do not default to a version 4 UUID for an authentication secret. UUIDs are identifiers. RFC 9562, section 8, warns against assuming UUIDs resist guessing or using them as security capabilities whose possession grants access.
Store credentials in a secrets manager or vault. Rotate or revoke exposed credentials. A leaked key works immediately. An attacker does not need to crack it.
See AI Agent Security: The Risk of an Unsecured Entry Point.
Never hand a secret to an AI model or a spreadsheet
- Never paste passwords, API keys, access tokens or other secrets into ChatGPT, Copilot, Claude or any other AI model.
- Never store passwords or API keys in Excel, Google Sheets or ordinary shared documents, even if labelled confidential. This includes browser notes and chat messages.
- Keep credentials out of AI prompts, conversation histories, transcripts, agent memory, source code and application logs.
- Use the approved password manager for human passwords and a dedicated secrets manager for API keys, OAuth tokens and AI agent credentials.
- Connect AI agents through secure integrations that never show the secret to the model.
Never give an AI model the secret itself. Give the application controlled access to the service instead.
What does multi-factor authentication protect?
MFA adds another proof of identity or combines protected factors. It reduces risk when a password is exposed.
A fake website can collect a password and a manually entered one-time code for an attacker to use before expiry. These codes are not phishing-resistant. CSA's MFA bypass advisory explains these attacks. Keep MFA enabled and prefer phishing-resistant passkeys or security keys where supported.
See Recognising Phishing and Fake Regulator Messages.
What is a passkey?
A passkey uses a cryptographic credential associated with a specific service. Compatible implementations prevent a phishing site on another domain from using it to sign in to the genuine service.
Check whether credentials sit on managed devices, in synchronised stores or on hardware keys. Plan how the firm recovers access after device loss.
What should a user do when a sign-in approval appears unexpectedly?
A staff member preparing a payroll reconciliation receives repeated prompts without starting a login. Approving one could grant someone else access.
Deny it, avoid linked messages and report through the firm's security channel. If compromise is suspected, follow recovery procedures using a separate trusted device or session as the response team instructs.
See Reporting and Containing a Cyber Incident at Work.
What should a small practice prioritise?
A Singapore practice using Xero, Microsoft 365, a bank portal and payroll should begin with accounts granting the widest access.
| Check | What to review |
|---|---|
| Credentials | Unique passwords, with secrets stored appropriately. |
| Authentication | MFA and supported phishing-resistant methods. |
| Recovery | Contacts and lost-device procedures without emergency shared passwords. |
| Administrative privileges | Who has administrative access. |
| Sign-in events | Visibility into suspicious activity. |
Key takeaways
- Remember a strong passphrase. Let your password manager remember the rest.
- Use random-word passphrases for passwords you must remember, such as a master password or Windows password.
- Use unique generated passwords for other applications.
- Prefer passkeys or other phishing-resistant sign-in where supported. Manually entered codes are not phishing-resistant.
- Store securely generated random secrets for API keys and machine credentials in a secrets manager.
- Never paste secrets into AI tools or spreadsheets.
- Deny and report unexpected sign-in prompts.
Last source check: 12 November 2026.
Next in the course: Securing Shared Devices, Access Rights and Staff Offboarding
Sources
- NIST: SP 800-63B Revision 4
- NIST: How Do I Create a Good Password?
- OWASP: Secrets Management Cheat Sheet
- Microsoft: Windows Hello for Business
- RFC 9562: Security Considerations
- Cyber Security Agency of Singapore: Passwordless authentication (2026)
- Cyber Security Agency of Singapore: MFA bypass advisory
Frequently asked questions
This information has been prepared for general informational purposes only and is not intended to be relied upon as accounting, tax, or other professional advice.


