https://github.com/disruptops/cred_scanner

A simple file-based scanner to look for potential AWS access and secret keys in files
https://github.com/disruptops/cred_scanner

Last synced: about 1 month ago
JSON representation

A simple file-based scanner to look for potential AWS access and secret keys in files

• Host: GitHub
• URL: https://github.com/disruptops/cred_scanner
• Owner: disruptops
• License: mit
• Created: 2018-05-16T04:55:56.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2024-03-18T21:47:51.000Z (9 months ago)
• Last Synced: 2024-08-01T08:10:37.118Z (4 months ago)
• Language: Python
• Size: 1.95 KB
• Stars: 87
• Watchers: 6
• Forks: 33
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-bbht - cred_scanner - (Content Discovery / AWS S3 Bucket)
• awesome-bbht - cred_scanner - (Content Discovery / AWS S3 Bucket)

README

        
# cred_scanner

A simple command line tool for finding AWS credentials in files. Optimized for use with Jenkins and other CI systems.

I suspect there are other, better tools out there (such as [git-secrets](https://github.com/awslabs/git-secrets/blob/master/git-secrets)), but I couldn't find anything to run a quick and dirty scan that also integrates well with Jenkins.

## Usage:

To install just copy it where you want it and install the requirements:

	pip install -r ./requirements.txt

This was written in Python 3.6.

To run:

	python cred_scanner.py 

That will scan the local directory and all subdirectories. It will list the files, which ones have potential access keys, and which files can't be scanned due to the file format. cred_scanner exits with a code of 1 if it finds any potential keys.

	Usage: cred_scanner.py [OPTIONS]

	Options:

	  --path TEXT  Path other than the local directory to scan

	  --secret     Also look for Secret Key patterns. This may result in many

	               false matches due to the nature of secret keys.

	  --help       Show this message and exit.

To run as a test in Jenkins just use the command line or add it as a step to your Jenkins build. Jenkins will automatically fail the build if it sees the exit code 1.