incident-disclosure: add Incident Disclosure and Notification policy #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
awly
force-pushed
the
awly/incident-disclosure
branch
from
2c4e500
to
221ea46
Compare
New policy to document our commitments to disclosing security incidents and the exact process for notifying users.
awly
force-pushed
the
awly/incident-disclosure
branch
from
221ea46
to
f9083a0
Compare
mayakacz
approved these changes
Jul 28, 2023
Co-authored-by: Maya Kaczorowski <15946341+mayakacz@users.noreply.github.com>
|
|
||
| To notify users about security vulnerabilities, Tailscale will **email** affected tailnets’ administrators, with information specific to the tailnet, including specific users or nodes which are affected. These emails will be sent to the [security contact](https://tailscale.com/kb/1224/contact-preferences/#setting-the-security-issues-email) for the tailnet, which by default is the Owner of the tailnet. | ||
|
|
||
| Occasionally, Tailscale may decide to notify users in additional ways about a security issue, such as by publishing a [blog post](https://tailscale.com/blog/), or with in-product notifications by putting a warning banner in the admin console. |
There was a problem hiding this comment.
To avoid ruling out other kinds of in-product notifications, suggestion:
... in-product notifications (such as by putting...).
Up to you though.
| @@ -26,7 +26,7 @@ All employees should watch for potentially suspicious activities, including: | |||
| * Modification or defacement of websites | |||
| * New open network ports on a system | |||
|
|
|||
| Tailscale regularly reviews logs for detecting and tracking attempted intrusions and other suspicious activity. These include git, cloud, networking, SaaS tool, and other infrastructure logs. | |||
| Tailscale regularly reviews logs for detecting and tracking attempted intrusions and other suspicious activity. These include git, cloud, networking, SaaS tool, and other infrastructure logs. | |||
There was a problem hiding this comment.
usage nit (up to you): "...reviews logs to detect and track..."
awly
added a commit
that referenced
this pull request
Jul 28, 2023
Post-merge suggestions from #12 (review)
awly
added a commit
that referenced
this pull request
Jul 31, 2023
Post-merge suggestions from #12 (review)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New policy to document our commitments to disclosing security incidents and the exact process for notifying users.