Skip to content

Latest commit

 

History

History
79 lines (63 loc) · 3.21 KB

File metadata and controls

79 lines (63 loc) · 3.21 KB
title slug policy faq weight
Information classification policy
information-classification
true
false
3

To understand its potential exposure from a security risk, issue or incident, Tailscale regularly catalogues and classifies its data and other in-scope assets, in order to apply risk-based controls.

Assets are anything that has value to the organization, including but not limited to, customer data, production data, financial data, intellectual property, and any material non-public information.

Asset cataloging

Tailscale catalogues assets with several pieces of information, to help identify the potential risk of the asset. Information collected is as follows:

  • Description, i.e. what is the asset?
  • Risk, i.e. what is the asset risk classification?
  • Use, i.e. how is this asset used?
  • Location, i.e. where is it stored, used, and backed up?
  • Sharing, i.e. is it shared with any third parties, such as vendors? Which specific third parties?

If new data is catalogued, or data use changes, it should be specifically reviewed to verify that its collection and use is in line with Tailscale’s Privacy Policy.

Asset risk classification

Tailscale classifies assets into three risk categories: Low Risk, Medium Risk, and High Risk. Definitions are as follows:

Risk category Definition
High risk
  • Data: protection is mandated by confidentiality agreements, labor codes, specific laws and regulations (e.g. PCI DSS, HIPAA, GDPR), or data is subject to breach reporting requirements, or disclosure would have a significant adverse impact on Tailscale (e.g., user accounts database).
  • Hardware and software systems: compromise would have a significant adverse impact on Tailscale (e.g. the login.tailscale.com control plane service).
Medium risk
  • Data: not generally available to the public, and disclosure would have some adverse impact on Tailscale (e.g. internal engineering documentation).
  • Hardware and software systems: compromise would have some adverse impact on Tailscale (e.g. cloud VM running production monitoring system).
Low risk
  • Data: publicly available, or disclosure would have no adverse operational or financial impact on Tailscale (e.g. tailscale.com website source code). May still have some limited reputational impact.
  • Hardware and software systems: compromise would have no adverse impact on Tailscale (e.g. testbed cloud VM with no user data or privileged access).

When multiple classifications may apply, the highest applicable classification is used. For example, if a machine is low-risk by itself, but can be used to access high-risk data, its overall classification is also high-risk.

Schedule

Tailscale should review the data it collects and processes, and update the data register, quarterly.