docs: Add secure collaboration learning path#29386
Open
jhutchings1 wants to merge 2 commits intoproductionfrom
Open
docs: Add secure collaboration learning path#29386jhutchings1 wants to merge 2 commits intoproductionfrom
jhutchings1 wants to merge 2 commits intoproductionfrom
Conversation
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
CI run failed: build logs |
Contributor
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This new learning path documents a number of security best practices for customers in terms of setting up an account, inviting collaborators, creating API tokens, creating developer products, and finally securing them behind Zero Trust. This is intended to be high level and guide folks to more specific docs that already exist.
@AdamBouhmad @irvinebroque @asamborski @dcpena would love to get your thoughts on this.
Screenshots (optional)
Documentation checklist