Skip to content

[Improve Existing Best Practice Guide]: Automated checking for general sensitive information within Git #89

@riverma

Description

@riverma

Checked for duplicates

Yes - I've already checked

Best Practice Guide

Continuous Integration

Best Practice Guide Sections

Starter Kits

Describe the improvement

We have some existing recommendations for checking sensitive AWS credential information via using git-secrets described here. However, we've received feedback that this could be improved via the following:

  • Sample pattern files to check for more specific sensitive information such as IPs, username / passwords, ARNs, security-groups
  • A GitHub-side automation that checks repositories even if folks have committed and pushed sensitive information

To support these two needs, we should evaluate if git-secrets is the right tool, or if it should be augmented or replaced with a better solution.

Metadata

Metadata

Assignees

Labels

medium complexityTicket is relatively straightforward but may have a difficult sub-taskmost requestedHighly requested by community memberssoftware lifecycleProcess improvements involving developing, testing, integrating, deploying software

Type

No type

Projects

Status

✅ Work Complete

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions