---
title: "Discussion on \"Keep Your Source Secure: Stop Committing Sensitive Information to Git\" | Hashnode"
description: "Discussion on \"Keep Your Source Secure: Stop Committing Sensitive Information to Git\". Do you have your security engineer running behind you to remove secrets off git? Or keep getting alerts in gitleaks or in your CI security scanning tool that someone inadvertently committed a secret in git? Developers might forget to sanitize the app..."
url: "https://hashnode.com/posts/keep-your-source-secure-stop-committing-sensitive-information-to-git/67963cab663f1abaa6bfc806"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Keep Your Source Secure: Stop Committing Sensitive Information to Git](https://maybeitdepends.com/keep-your-source-secure-stop-committing-sensitive-information-to-git?utm_source=hashnode&utm_medium=feed)

Do you have your security engineer running behind you to remove secrets off git? Or keep getting alerts in gitleaks or in your CI security scanning tool that someone inadvertently committed a secret in git? Developers might forget to sanitize the app...

Jan 26, 2025 · 3 min read · maybeitdepends.com  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#aspnet-core](https://hashnode.com/tag/aspnet-core)
-   [#keyvault](https://hashnode.com/tag/keyvault)
-   [#appsettings](https://hashnode.com/tag/appsettings)

## Written by

[Narayana Rengaswamy](https://hashnode.com/@rnarayana)

@rnarayana · Bangalore, India

  
[View profile](https://hashnode.com/@rnarayana)

Software Architect, Sci-fi and fantasy enthusiast, Dad & Husband

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
