- Personnel policy
- Risk assessment policy
- Information classification policy
- Third party vendor review policy
- Incident disclosure and notification policy
- Incident response policy
- BCP/DR policy
- Access control policy
- Password policy
- Change management policy
- Testing policy
- Patch management policy
- Data retention and deletion policy
Incident response process
When a suspected incident is reported, it is first investigated by the SIGENG oncall. If it is suspected to be an incident, they should declare an incident, and identify the Incident Commander in the #incident-response Slack channel. The Incident Commander is responsible for:
- If an incident is likely to require ongoing response and remediation efforts, opening a GitHub issue in the tailscale/corp repo to track updates to the incident and creating a Google doc for collaborative work.
- Classifying the severity of the incident, including scope and the risk of any assets which may be affected. This can be further updated as information changes, and may inform how we choose to react. Depending on the urgency of the incident, this may be done after the fact.
- Contacting vendors or coordinating to contact vendors, to validate if their product may be compromised.
- Appointing roles, including a communications lead, if needed.
- Ensuring handoff between team members, for example, at the end of a work day.
- Escalating to leadership if responses are insufficient.
In addition to remediating the incident, Tailscale employees should also seek to put into place any corrective actions possible to lessen the impact of an incident.
If an incident affects customers, including their data or their ability to use Tailscale, Tailscale may choose to proactively communicate the issue publicly.
If data or processes were disrupted by the incident, then the BCP/DR policy should be followed to remediate the issue.
Once an incident is mitigated or otherwise closed, it is the Incident Commander’s responsibility to ensure that
- The resolution is communicated to all affected parties, including external customers, if applicable.
- For incidents causing a production outage or loss of customer or other critical data, a post-mortem is completed. This should include: details of the incident, timeline of the incident, its impact, the actions taken to mitigate or resolve it, the root cause(s), and the follow-up actions to prevent the incident from recurring. Where applicable, some version of the post-mortem may be shared with external affected parties. Newly identified risks should be added to the risk register.
An incident is an adverse event which affects Tailscale’s infrastructure or business operations in such a way that it compromises our ability to deliver the service customers expect. A vulnerability is not necessarily an incident; for example, a vulnerability not being actively exploited may require action, but not expedited action beyond existing vulnerability remediation processes.
Incidents can be classified based on their severity:
|Extreme or complete production outage, significantly degraded experience for >50% of Tailscale users, or customer or other critical data loss or corruption.
|Partial outage of some production functionality or in some regions, degraded experience for multiple customers with no workaround available, or suspected severe security breach.
|Non-critical functionality loss or degradation for some customers, with possible short-term workaround, or detection of unauthorized activity.
|No current or known customer impact.