Open Fennerr opened 11 months ago
More secrets to consider:
AWS CodeCommit:
AWS Elastic Container Registry (ECR):
AWS Lambda Layer Contents:
AWS Systems Manager State Manager:
AWS Batch Job Definitions:
Amazon SageMaker:
AWS Amplify Console:
AWS Data Pipeline:
AWS Glue Data Catalog:
Hi @Fennerr, all of them interesting ideas, but maybe we need to rethink a little bit our "secrets detection engine" ...
The detect-secrets
package generates false positives and the current way of scanning generates a lot of resource exhaustion ...
This is true. Maybe move it to an optional flag and/or a config option to select what secrets you want to scan for
It would also be nice to generalize the way that secrets are scanned for so that stuff like writing to the temp files to disk, search for secrets, and using multiprocessing for this (as it's cpu intensive) can just be handled in one place.
@Fennerr Was there any decision on this ticket going forward? Because if the detect-secrets package is going to be changed I would love to work on that. Thanks!
Hello @Gfuen there are no plans on changing the detect-secrets
package. Do you have any suggestion for a different Python package to look for secrets?
Related to the checks requested above they are still pending to be done.
New feature motivation
Similar to the secrets checks for the other services (lambda/ec2/ecs/etc), more checks can be implemented
Solution Proposed
Elastic Beanstalk:
API Gateway:
CodeBuild and CodePipeline:
Glue Jobs:
Step Functions:
AppSync:
This might not be all the API calls that need to be made to get the secrets, but should be a good starting point
Describe alternatives you've considered
None
Additional context
No response