Password and Authentication Policy template (free, plain-language starter)

Free password and authentication policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certification.

Template · Updated · by the Controlkeep team

In short

Password manager, passphrase rules, multi-factor authentication and how credentials are handled. This free starter covers 2 controls and leaves 4 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.

Password manager, passphrase rules, multi-factor authentication and how credentials are handled. Customers and auditors ask for it in enterprise customers checking MFA; write it early: MFA is the cheapest big risk reduction.

Starter policies are original templates written by Controlkeep. They are a starting point, not legal advice, and adopting them is not a certification or an audit opinion. Adapt every rule to how your company really works, and have a qualified adviser review policies with legal effect (privacy, employment, contracts).

Controls it supports

RefControlStarter framework
TC-ACC-04Strong authenticationSOC 2-style common criteria starter
IS-TEC-03Secure authenticationISO 27001-style Annex A starter

Decisions to make before approving

  • [password manager name]
  • [identity provider]
  • [5 minutes]
  • [12 months]

The policy text

Purpose

Most account takeovers start with a weak, reused or stolen password. This policy sets simple rules that make [Company] accounts hard to break into.

Scope

Every account used for [Company] work: company accounts, admin accounts, service accounts, and personal devices used to access company systems.

Passwords and passphrases

  1. Use the company password manager ([password manager name]) to generate and store passwords. Its master password must be a long passphrase that you use nowhere else.
  2. Passwords must be at least 12 characters (14 or more for admin accounts). Long passphrases are encouraged; forced complexity rules are not required.
  3. Never reuse a work password on any other account, work or personal.
  4. Change a password immediately if it may have been seen by someone else, appeared in a breach, or was sent in plain text. Routine forced changes are not required otherwise.
  5. Never share passwords. Shared team credentials, where unavoidable, are stored in a shared vault in the password manager, never in documents or chat.

Multi-factor authentication (MFA)

  1. MFA is required on email, the password manager, cloud and hosting accounts, code repositories, finance systems, and any system holding customer data.
  2. Prefer phishing-resistant methods (security keys or passkeys), then authenticator apps. SMS codes are used only where nothing else is available.
  3. Never approve an MFA prompt you did not start. Report unexpected prompts to [Security Contact].
  4. Recovery codes are stored in the password manager.

Single sign-on

Where a system supports single sign-on with the company identity provider ([identity provider]), it must be used, so that leaving the company disables access everywhere at once.

Devices

Company devices must use a screen lock (PIN, password or biometrics) that activates after no more than [5 minutes] of inactivity.

Service accounts and API keys

Secrets used by software are stored in a secrets manager or the platform's encrypted settings, never in source code, and are rotated at least every [12 months] or when someone with access leaves.

Lockout and monitoring

Systems should limit repeated failed sign-in attempts where they offer it. Unusual sign-in alerts are reviewed by [Policy Owner].

Exceptions

Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.

Enforcement

Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.

Review

[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].

Adopt it

  1. Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
  2. Decide the 4 remaining bracketed items so the rules match how you actually work.
  3. Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.

Related: collecting audit evidence, policies help, Incident Response Policy, Vendor and Third-Party Management Policy.

Questions and answers

Should the policy force password changes every 90 days?

This starter does not require periodic changes for strong unique passwords; it requires changes after suspected compromise. Adjust it if a customer contract says otherwise.

Does adopting this password and authentication policy make us SOC 2 or ISO 27001 compliant?

No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.