NEW: Securing developer workspace guide #184084
Replies: 4 comments 1 reply
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Don’t miss the new content, Securing developer workspace, we added to our GitHub Well Architected library on prescriptive guidance for application security.
We have specific recommendations that offer expert opinions and actionable prescriptions in the context of the Application Security space 🔒. We’ll discuss various trade-offs and considerations to help you make informed decisions tailored to your unique context.
In the latest article, Securing developer workspace, an Application Security guidance for hardening developer workspaces, including identity and authorization, workspace isolation, and signed commit practices.
Stay tuned for more announcements as we continue to add content.
Let us know your thoughts on the new guide and any recommendations you have for a secure developer workspace in the comments section.
Tip
The GitHub Well-Architected Framework is an open source-style, community-driven framework to curate the best way to deploy the GitHub platform. Learn more at https://wellarchitected.github.com/
Beta Was this translation helpful? Give feedback.
All reactions