password policy

Password policy for a small business: rules staff can follow

AA
Aurum Avis Labs Author
6 min read

Password policy for a small business: keep it short and enforceable

A password policy for a small business tells staff how long passwords must be, whether they may reuse them across sites, and what to do when someone leaves. In Switzerland, firms with 20 to 250 employees rarely have a dedicated identity team; the policy must fit on one page and work with Microsoft 365 or Google Workspace defaults. Art. 8 FADP expects appropriate technical and organisational measures; a written rule set is part of that, without claiming an audit is solved by paper alone. This article is a checklist for a template, not the password manager comparison and not a shared team password in chat.

Strong accounts reduce mailbox takeover that feeds invoice fraud with a changed IBAN. Report suspicion through internal incident reporting, not a casual forward. Payment release stays a separate process: four-eyes principle for payments.

  • Minimum length and ban on reusing work passwords on private shopping sites
  • Mandatory MFA on email and admin accounts, documented in a separate rollout plan
  • No shared logins; named accounts for e-banking approvers
  • Offboarding checklist that disables accounts the same day
  • Report suspected compromise through the internal hotline, not by email alone

What to put in the written policy

State who the policy covers: employees, contractors with company mail, and anyone with VPN access. Define minimum password length aligned with your identity provider; many Swiss SMEs use 12 characters or more with block lists for obvious words. Require unique passwords for work systems. Forbid storing passwords in plain text in Teams chats, tickets, or Excel on a shared drive.

Add what happens after a phishing click: reset the password and report the incident. State that the helpdesk never asks for the full password on the phone.

A made-up example: a 60-person trading company publishes a one-page German policy. It says passwords are personal, MFA is required on Microsoft 365, and the helpdesk never asks for a password on the phone. New hires sign the IT acceptable-use appendix on day one.

Include

  • Length, uniqueness, MFA expectation
  • How to report a suspected phished password
  • Rules for admin and finance roles

Skip or keep minimal

  • 90-day rotation with no MFA (often harmful)
  • Complexity rules that push Post-it notes
  • Legal quotes without plain-language duty

Roll out the policy in one working day

  1. Match technology

    Check password length and legacy auth in the admin centre. Turn on MFA for email and admins, or set a fixed go-live date.

  2. Write the one-pager

    Scope, length, ban on shared logins, reporting path, offboarding in plain language.

  3. Align HR and helpdesk

    Offboarding list and reset process: verify identity before reset using an HR rule, no reset because “the boss emailed” without callback.

  4. Publish and explain briefly

    Intranet, onboarding, five minutes in a team meeting. Keep attendance notes when audit or insurance asks.

Admin, finance, and break-glass accounts

Name fewer super-admins than you think you need. Finance e-banking must use named users with dual authorisation, not a shared “finance” login. Break-glass emergency accounts should be sealed, logged, and reviewed quarterly. When someone in HR or finance leaves, trigger the same access removal as for IT.

What the policy should not pretend to solve

A policy does not stop CEO fraud by itself. It does not replace four-eyes controls on payments. It is not a substitute for a business password manager; that comparison is a separate article. Shared logins in Teams or Excel stay forbidden even when the policy says so, unless technology enforces named accounts.

Penalties should be proportionate; the goal is clarity, not fear. Physical notes with passwords belong in clean desk and disposing of files, not under the keyboard.

Microsoft 365 and Google Workspace

Set password length policies in the admin centre, block legacy auth, and pair with MFA. Screenshot settings for audit evidence. Record who may change conditional access or similar rules for finance roles.

List global admins quarterly. Reserve break-glass for emergencies, not daily work by leadership.

Who can skip a long policy

Below roughly ten people with no shared systems, MFA plus a spoken rule may be enough if offboarding is documented. Groups with a central identity team use their own standards, not this one-page template.

When every app has a shared password in chat, paper is not enough: remove shared logins first, then policy and optionally a vault.

  • Fiduciary with client mailboxes

    Separate accounts per staff member; no shared portal password. MFA on mail that approves invoices.

  • Contractor firm with subs

    Time-bound accounts for site apps, expiry at project end. No firm password forwarded by SMS.

  • Practice with evening cover

    No shared login at reception overnight; each role has its own account with MFA on mailbox.

Insurance questionnaires and audit

Questions often cover minimum length, MFA, and proof of training. Answer with the intranet version and live-session attendance, not claims the text does not support. Admin-centre screenshots back the one-page policy.

Password spraying and leaked lists are reasons for uniqueness and MFA, not weekly rotation. After a phishing click: change password, sign out sessions, report the incident. The same line belongs in the policy and in onboarding.

Must we change passwords every 30 days?

Modern guidance favours length, uniqueness, and MFA over frequent rotation that pushes people to patterns. Align with your cloud provider and insurer questions, and document the choice in writing.

Contractors, temps, and shared accounts

Contractors get their own login with an expiry date, not a colleague’s password. Do not share shop admin, social media access, or the info@ mailbox; exceptions need a written end date and owner. IT tickets and project tools are not password stores.

  • Length12+ characters

    Typical on Microsoft 365 and Google, plus block lists.

  • MFAEmail + admin

    Start where mailbox and tenant rights sit.

  • RotationOn suspicion

    Not blanket 30-day cycles without MFA.

Helpdesk, reset, and offboarding

Verify identity before reset using a process HR agrees on. Never reset because “the boss emailed” without callback. On exit: disable accounts the same day, not “just quick portal access”. Use the same checklist as for laptops and keys.

Keep prior PDF versions with dates when auditors ask what applied in March versus June. One owner updates the intranet page and records the version date.

Live session when audits ask for evidence

Auditors and insurers often ask whether staff were told the rules. A one to two hour live session with attendance notes beats an unread PDF. Topics: phishing, MFA fatigue, payment fraud, reporting path. Details on the security awareness training page.

After an incident, review rules, not only reset passwords. Was MFA on? Was the account shared? Record actions taken and repeat the session if the rule was signed but not understood. Leadership should not get informal exceptions: break-glass and admin rules apply there too.

One slide for the board is enough: duties, what IT enforces automatically, how staff report suspicion. Mention training aligned with FADP and GDPR practice without claiming “compliance” from paper alone.

password policy access control sme switzerland
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.