On This Page
- Personnel policy
- Risk assessment policy
- Information classification policy
- Third party vendor review policy
- Incident disclosure and notification policy
- Incident response policy
- Incident response process
- BCP/DR policy
- Access control policy
- Change management policy
- Testing policy
- Patch management policy
- Data retention and deletion policy
To avoid potential security incidents, Tailscale requires employees to follow password requirements.
This policy applies to passwords for any application or server accessed by Tailscale employees, contractors, or vendors. It does not apply to the passwords customers of Tailscale use to access the Tailscale service.
Passwords must be unique for each use.
Passwords must be randomly generated.
Default passwords on all systems are changed after installation. Initial passwords generated for new users must be changed after login.
Passwords do not need to be regularly rotated. However, if a password is known or thought to be compromised, it must be rotated to a new password.
Where a third-party application supports single sign-on, it must be used.
Where a third-party application supports multi-factor authentication, it must be used. Use of multi-factor is enforced where possible.
Acceptable forms of multi-factor authentication include authentication apps or a WebAuthn token. Embedded tokens (e.g., TouchID) are permitted. WebAuthn hardware or embedded hardware tokens are preferred to authentication apps.
Where SSO is not used, and where possible, passwords should be stored in a password manager.
Encryption at rest
Passwords should be stored encrypted at rest.
Passwords should not be logged.
Requirements for specific use cases
Access to servers, for both production as well as development and testing infrastructure, must be with a password and MFA or with per-user public keys (e.g., SSH keys). Only Tailscale-based network authentication is permitted for services not exposed to the Internet.
Automated processes, including deployment or CI/CD tools, should use passwords or API keys to access and communicate with other systems. Passwords used in scripts must be encrypted at rest.
End user devices
End user devices must use passwords to encrypt their disks and unlock the device. These must be unique for each individual but may be reused across an individual’s devices. These do not need to be randomly generated.
SaaS applications or other software
Access to third party applications must use SSO where possible, MFA where possible, and enforce MFA where possible.
An individual’s password for their password management vault must be unique. These do not need to be randomly generated.