Executable Tutorial delivery: Gitleaks #2918
Merged
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
Gitleaks: Detecting secrets in Git repositories
Names and KTH ID
Deadline
Category
Description
We aim to illustrate how to use Gitleaks to automatically detect and prevent secrets (API keys, passwords, tokens, certificates) from being committed to Git repositories. The tutorial will cover:
The tutorial will use practical examples with repositories containing simulated secrets, showing how Gitleaks can detect them and how developers can remediate the issues.
Relevance
Secret sprawl is one of the most common security risks in DevSecOps. Tools like Gitleaks helps to prevent credentials from ever reaching version control. This knowledge is highly relevant for DevOps engineers, since mismanaged secrets can lead to major security breaches and compliance issues, even on private repositories.
Deliverables
Tutorial: https://killercoda.com/stagge/scenario/gitleaks-tutorial
Repository: https://github.com/Stagge/gitleaks-tutorial