Home / Companies / GitGuardian / Blog / June 2020

June 2020 Summaries

2 posts from GitGuardian

Filter
Month: Year:
Post Summaries Back to Blog
The tutorial guides users on how to scan files and directories for sensitive information, such as API keys or credentials, using the GitGuardian API and its Python wrapper. It explains the setup process, including installing the necessary Python client, obtaining an API token, and setting up environment variables. The tutorial details how to write a Python script that uses the GitGuardian API to detect and report policy breaks, such as high-risk file extensions or filenames, and outputs the results in JSON format. Users learn to handle API limitations by processing files in manageable chunks and printing detailed results, including policy break types and matches. The tutorial emphasizes best practices, such as not hardcoding secrets and considering any exposed secrets as compromised.
Jun 29, 2020 2,209 words in the original blog post.
Managing secrets such as API keys and credentials is a complex task that requires a proactive and informed approach, as even stringent policies can be bypassed for convenience. Best practices for secret management include avoiding the storage of unencrypted secrets in git repositories, refraining from using wildcard commands that may inadvertently capture sensitive files, and not relying solely on code reviews to catch secret leaks. The use of automated secret scanning tools, like GitGuardian, is emphasized to enhance visibility and detect hidden secrets. Encrypting secrets within repositories, using environment variables, and considering "Secrets as a Service" solutions like Hashicorp Vault or AWS Key Management Service are recommended strategies. Restricting API permissions, IP whitelisting, and employing short-lived secrets are crucial for limiting potential damage and unauthorized access. Ultimately, secret management is a continuous, active strategy that must be customized according to the project's specific needs and requires ongoing vigilance from developers.
Jun 12, 2020 1,984 words in the original blog post.