Skip to content

Conversation

@Stagge
Copy link
Contributor

@Stagge Stagge commented Oct 8, 2025

Assignment Proposal

Title

Gitleaks: Detecting secrets in Git repositories

Names and KTH ID

Deadline

  • Task 3

Category

  • Executable tutorial

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:

  • Installing and configuring Gitleaks locally and in CI pipelines
  • Running scans on existing repositories and interpreting the results
  • Writing and customizing Gitleaks configuration files (regex patterns, allowlists)
  • Demonstrating integration into Git hooks to block commits containing secrets

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

@sofiabobadilla
Copy link
Collaborator

We have received the submission.

The task will be graded in the upcoming weeks, and the grades will be reported on canvas.

Thank you for your work.

@sofiabobadilla sofiabobadilla self-assigned this Oct 9, 2025
@sofiabobadilla sofiabobadilla merged commit e936bee into KTH:2025 Oct 9, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants