Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Trufflehog Update] Add Trufflehog secret scanning workflow #1035

Closed
5 tasks done
matbmoser opened this issue Sep 18, 2024 · 2 comments · Fixed by #1049
Closed
5 tasks done

[Trufflehog Update] Add Trufflehog secret scanning workflow #1035

matbmoser opened this issue Sep 18, 2024 · 2 comments · Fixed by #1049

Comments

@matbmoser
Copy link
Contributor

matbmoser commented Sep 18, 2024

Description

The GitGuardian secret scanning tool licence is now expired, therefore in order to maintain the Security of the Tractus-X Repositories there will be inforced the TRG-8.03 for all Tractus-X repos.

Incident Ticket

eclipse-tractusx/sig-security#86

Your repository was found in one of our security scans, and it was listed along with other repositories for not contain any of this files:

".github/workflows/trufflehog.yaml"
".github/workflows/trufflehog.yml"
".github/workflows/secrets-scan.yml"

Please read the TRG-8.03 and create the workflow file as soon as posible!

What needs to be done?

  • Add the Trufflehog workflow like described in TRG-8.03 to the /.github/workflows folder
  • Remove all references to GitGuardian from documentation
  • Create a PR and Merge it to main
  • As committer: revise if any secrets were found in the scan (in the security tab)
  • Close this ticket

Thank you very much for doing the update! 🚀

If there is any question, please let us know,
Your Tractus-X Project Leads 💯

@matbmoser
Copy link
Contributor Author

I am taking care here

@matbmoser
Copy link
Contributor Author

Done

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 a pull request may close this issue.

1 participant