Security

Password & Authentication Policy

How UKBH protects access to business systems, customer information and cloud services.

Effective from: 2 September 2026

This policy sets out how UK Business Hosting (“UKBH”) protects access to business systems, customer information, development systems and cloud services through passwords, passkeys and other authentication methods.

The aim of this policy is to ensure that authentication credentials are difficult to guess or steal, are not reused across systems, and are changed promptly where compromise is suspected.

Owner: Keith Davis trading as UK Business Hosting

Effective from: 2 September 2026

Review frequency: At least annually, and after any significant security incident or material change to UKBH systems.

1. Purpose

UK Business Hosting uses passwords, passkeys and other authentication methods to protect business systems, customer information, development systems and cloud services.

The aim of this policy is to ensure that authentication credentials are difficult to guess or steal, are not reused across systems, and are changed promptly where compromise is suspected.

2. Individual accounts

Every person requiring access to a UKBH system must use their own account wherever the service supports individual user accounts.

Shared usernames and passwords should not be used.

UKBH is currently operated by one person. If additional users are introduced in future, each person must receive their own account and access appropriate to their role.

3. Default passwords

Default manufacturer, installer or supplier passwords must be changed before a device or service is used for UKBH business purposes.

This applies where relevant to:

  • routers and network equipment;
  • computers and mobile devices;
  • software and administrative systems;
  • hosting or server-management systems;
  • any other device supplied with default credentials.

Known default credentials must not remain active.

4. Unique passwords

Passwords used for UKBH must be unique to each system or service.

A password used for one UKBH account must not be reused for:

  • another UKBH service;
  • a personal account;
  • another organisation.

Passwords exposed in a breach must never be reused.

5. Password quality

Where passwords remain necessary, UKBH should use long, strong passwords generated or stored securely.

Where a service does not provide an appropriate stronger authentication control, passwords should normally contain at least 12 characters, with no unnecessary maximum-length restriction.

Passphrases based on multiple unrelated words are acceptable where appropriate.

Passwords should not be based on easily guessed information such as:

  • names;
  • birthdays;
  • pet names;
  • business names;
  • keyboard patterns;
  • common passwords.

This matches the current Cyber Essentials technical approach of using MFA or appropriate password-length/common-password controls.

6. Password manager

UKBH should use a reputable password manager or equivalent secure credential-storage mechanism for unique credentials that cannot reasonably be remembered.

Passwords must not be stored:

  • in plain-text files;
  • in source code;
  • in GitHub repositories;
  • in website code;
  • in public or customer-accessible records.

Secrets, tokens and API keys should use appropriate secure secret-management facilities.

7. Multi-factor authentication

MFA must be enabled for UKBH cloud services wherever the service provides it.

This is particularly important for services containing:

  • customer data;
  • source code;
  • domains;
  • hosting;
  • email;
  • administrative access;
  • development systems.

Cyber Essentials v3.3 requires MFA for authentication to cloud services.

Where available, UKBH should prefer strong methods such as:

  • passkeys/security keys;
  • authenticator applications;
  • other secure MFA mechanisms provided by the service.

SMS may be used where a stronger supported method is unavailable.

8. Passwordless authentication

Where an established service supports secure passwordless authentication such as:

  • passkeys;
  • biometric authentication;
  • hardware security keys,

UKBH may use this instead of a traditional password where appropriate.

Passkeys can provide strong cryptographic authentication and are recognised in current Cyber Essentials guidance.

9. Protection against brute-force attacks

UKBH should only use authentication systems that provide reasonable protection against repeated password guessing.

Protection may include:

  • MFA;
  • throttling repeated attempts;
  • temporary account locking;
  • suspicious-login detection;
  • rate limiting;
  • passkeys or equivalent cryptographic authentication.

Cyber Essentials allows MFA, throttling or account/device lockout as means of protecting password authentication against brute-force guessing.

10. Administrative accounts

Administrative access should only be used where administrative privileges are required.

Where a service allows separate administrator and ordinary accounts, UKBH should use the administrative account only for administrative work rather than routine browsing, email or other unnecessary activity.

11. Suspected compromise

If a password, account, device or authentication method is believed to have been compromised, UKBH will act promptly.

The response should include as appropriate:

  • change or reset the affected password;
  • revoke active sessions;
  • revoke compromised API keys or access tokens;
  • review recent account activity;
  • enable or reset MFA;
  • check related accounts for reuse of the affected credential;
  • update the Asset Register/security records;
  • assess whether customer or personal information may have been affected;
  • take any required data-breach action.

A compromised password must not subsequently be reused.

12. Account removal and access review

Accounts or privileges that are no longer needed should be disabled or removed.

UKBH should periodically review:

  • administrative accounts;
  • cloud services;
  • connected applications;
  • API keys;
  • authorised devices;
  • MFA configuration.

13. Third-party access

If a contractor, supplier or other third party is ever given access to UKBH systems:

  • they should receive their own credentials where possible;
  • access should be limited to what is necessary;
  • MFA should be used where available;
  • access should be removed when the work ends.

UKBH credentials must not simply be handed to a third party where an individual account can be created instead.

14. Review and evidence

Compliance with this policy should be reviewed alongside the UKBH Asset Register.

For cloud services, UKBH should record:

  • whether MFA is available;
  • whether MFA is enabled;
  • whether privileged/admin access exists.

This policy should be reviewed at least annually and when there is a significant change to UKBH infrastructure.