Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ericalexanderorg/should-i-trust
OSINT tool to evaluate the trustworthiness of a company
https://github.com/ericalexanderorg/should-i-trust
Last synced: 3 months ago
JSON representation
OSINT tool to evaluate the trustworthiness of a company
- Host: GitHub
- URL: https://github.com/ericalexanderorg/should-i-trust
- Owner: ericalexanderorg
- Created: 2018-06-09T17:03:32.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-12-07T16:49:50.000Z (almost 5 years ago)
- Last Synced: 2024-01-23T12:54:02.321Z (10 months ago)
- Language: JavaScript
- Size: 400 KB
- Stars: 39
- Watchers: 3
- Forks: 10
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Changelog: change-log.md
Awesome Lists containing this project
- awesome-hacking-lists - ericalexanderorg/should-i-trust - OSINT tool to evaluate the trustworthiness of a company (JavaScript)
README
# should-i-trust
## Summary
-------------
should-i-trust is a tool to evaluate OSINT signals for a domain.
## Requirements
-------------
should-i-trust requires API keys from the following sources:
[Censys.io](https://censys.io/register) - Free for for first 250/quries/month
[VirusTotal](https://www.virustotal.com) - Free
[GrayHatWarFare](https://buckets.grayhatwarfare.com/register) - Free with limited results
### Use Case
-------------
You're part of a review board that's responsible for evaluating new vendors. You're specifically responsible for
ensuring new vendors meet compliance and security requirements.
Standard operation procedure is to ask for one or all of the following: SOC report, VSAQ, CAIQ, SIG/SIG-Lite. All
vendors will not have these reports and/or questionnaire answers. Maybe it's org process to deny vendor intake
without this information, or maybe, this is a "special" engagement and you need to ascertain trustworthyness without
the docs. Maybe you don't trust the response in the docs.
should-i-trust is a tool to go beyond standard responses and look for signals that the organization should not be
trusted. Maybe they're exposing their CI/CD to the internet with no auth. Maybe they have an EC2 instance with prod
code running and no directory restrictions.
should-i-trust doesn't provide all the information you will need to make a go/no-go decision but it will allow you
to quickly gather OSINT data for further evaluation.
should-i-trust is also useful for red team or similar engagements. It can quickly identify targets to probe.
### Setup
-------------
Either [install the chrome extension through chrome](https://chrome.google.com/webstore/detail/should-i-trust/hocfamfiidomggjegfgenhgaaifjjmla) or download and manually install in chrome using [developer mode](https://developer.chrome.com/extensions/faq).
### Running
-------------
> Open the extension
> Enter your API keys (required once)
> Enter a domain to query
### Output
-------------
+ If there's an indicator the domain participates in a bug bounty program
+ Domains found through VirusTotal, Censys.io, and the Google Cert Transparency Report
+ IPs and open ports found through Censys.io
+ Repositories found on GitHub, GitLab, and Bitbucket
+ Misc data found on virustotal.com
+ AWS bucket files found exposed through GrayHatWarfare
### Road Map
TBD