Tutorial Submission: Managing team secrets using Infisical and GitHub #2911
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.
Assignment Proposal
Title
Managing team secrets using Infisical and GitHub
Names and KTH ID
Deadline
Category
Description
Managing environment secrets is crucial, especially for developers working in teams. In this tutorial, we want to utilize Infisical and GitHub to show the following scenario:
Start with a condition where secrets are committed in plaintext to a GitHub repository
How to set up Infisical's Secret Scanning to scan existing GitHub repository and prevent future vulnerabilities
How to securely set up secrets in Infisical
How to consume Infisical secrets in runtime and use it for your application
With this tutorial, we want to highlight the before (unmanaged/unsafe) vs after (managed/safe) condition. We plan to deliver our tutorial on KillerCoda.
Infisical is chosen in the tutorial as an open-source alternative to HashiCorp Vault to manage secrets that teams can self-host. However, in this tutorial, we will use their cloud solution which has a Free plan that can be used for the scenario.
Relevance
Managing secrets is central to DevSecOps because it reduces the risk of credential leaks and aligns security with delivery workflows.
Link to tutorial
The tutorial can be accessed here: https://killercoda.com/noizy-sthlm/scenario/scenario